Specialist Repair Marketplace for No-Code Builders

AI Prompts to Build This

Copy these build prompts into Claude, Cursor, or your AI coding tool. Create a free account to unlock the full research behind them.

1. 1. Project Setup

   Build the weekend MVP of "TaskPatch": a board where a no-code builder posts a break and one verified specialist claims it. Payment is settled between the two outside the app this weekend; the app holds no money.
   
   Stack: Next.js (App Router), TypeScript, Tailwind, Supabase (Postgres, Row Level Security, Auth with email magic link), Resend for claim, confirm and dispute emails. Deploy on Vercel.
   
   Tables (Row Level Security on; posters edit their own tickets, specialists read open tickets and their own claims):
   - profiles(user_id, role, display_name)  role is poster, specialist or admin
   - specialist_profiles(user_id, platforms text[], bio, completed_count, avg_hours_to_close, accuracy_score, verified boolean)  you set verified by hand
   - tickets(id, poster_id, platform, title, repro, budget_cents, status, specialist_id, created_at)  platform comes from a fixed list of no-code platforms kept in one file; status is open, claimed, in_progress, complete, disputed or cancelled
   - claims(id, ticket_id, specialist_id, claimed_at)  unique on ticket_id
   - reviews(id, ticket_id, rating, hours_to_close, note)
   
   Screens: /login, /board (public), /tickets/new, /tickets/[id], /inbox (specialist), /admin/disputes.
   Env vars (names only): NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY (server only), RESEND_API_KEY.
   
   Do not build: billing, escrow or payouts, Stripe, bumps or a priority tier, proposals, chat or hourly tracking, an Airtable back office, AI ticket rewriting.
   Done when: npm run dev starts, you can sign in, and the five tables exist with Row Level Security on.

2. 2. Core Feature

   Build the one feature that proves TaskPatch: a ticket that exactly one specialist can claim, and a trust score that grows from real fixes.
   1. /board is public and lists open tickets with a platform badge, the budget, the age and a Filter by platform control, newest first.
   2. A poster creates a ticket with a platform from the fixed list (Bubble, Webflow, Make, Zapier or Airtable to start), a title, a reproduction description and a budget the two sides have agreed in advance.
   3. A verified specialist presses Claim. Insert a claims row; the unique key on ticket_id means the second of two simultaneous claims fails with "Someone just claimed this". Set the ticket to claimed and email both sides through Resend. The poster sees the specialist's platforms, completed count and accuracy score.
   4. The specialist marks in_progress. The poster presses Confirm fix, which sets complete, or Open dispute, which sets disputed and lists it on /admin/disputes as a plain table.
   5. After a confirmed fix the poster leaves a 1 to 5 rating and the hours it took. Update the specialist's completed_count, average hours and accuracy score from all their reviews.
   6. Emails use plain templates for claimed, confirmed and disputed.
   Rules: one claim per ticket. Say on every ticket page: "TaskPatch does not hold or move money in this version. Agree payment with the specialist before work starts." Only verified specialists can claim.
   Empty state: an empty board says no breaks are open and links to the post form.
   Done when: two simultaneous claims produce one claim and one refusal, both parties get an email, a confirmed fix updates the specialist's stats, and a dispute appears on the admin table.

3. 3. Landing Page

   Build a one-page landing site for TaskPatch, a repair board for no-code builders.
   Hero: "Post the break. A specialist who has fixed it before claims the ticket." Sub: "Bubble, Webflow, Make, Zapier and Airtable. No profile browsing, no proposals." Two buttons: Join the waitlist as a builder, Join as a specialist.
   Sections: a sample ticket card marked as an example, how it works in four steps (post the break, a specialist claims it, the fix, a score), a strip of the platforms covered, and an FAQ on how payment works today (between you and the specialist, outside the app), how disputes are handled and how specialists are verified.
   Waitlist: store the email and the role in a waitlist table in Supabase. No other service.
   Style: Geist, an off-white background, near-black type, one lavender accent.
   Done when: the page renders on a phone and a submitted email with its role appears in the waitlist table.

4. 4. Branding Package

   Use a design or image tool for this one. A coding agent cannot draw a logo.
   Brand for TaskPatch: a wordmark and an icon that suggest a square patch stitched over a crack.
   Colors: off-white, near-black and one lavender. Type: Geist, with tabular numbers for budgets.
   Deliverables: wordmark, icon, five platform tags that differ by shape and letter as well as color, four ticket status chips (open, claimed, complete, disputed), and one launch graphic.
   Done when: each deliverable is saved in one folder and the status chips are distinguishable without color.