Vibe Coders for Hire

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 "VibeCoders": a founder describes a project and sees the three best-fit vetted developers, and developers apply through a short vetting flow an admin reviews. No payments yet.
   
   Stack: Next.js (App Router, TypeScript), Tailwind, Supabase (Postgres, Row Level Security, Auth with email magic link and roles), the OpenAI API (a small model) to read a project description, Resend for emails. Deploy on Vercel.
   
   Tables (Row Level Security on; founders read their own projects and matches, developers their own profile, admins everything):
   - profiles(user_id, role, display_name) role is founder, developer or admin; you set admin by hand
   - developer_profiles(user_id, stack text[], ai_tools text[], hourly_rate, sprint_rating, status, github_url, sample_url, loom_url) status is pending, active or rejected
   - projects(id, founder_id, name, description, stack text[], timeline, budget_range, parsed jsonb, status)
   - matches(id, project_id, developer_id, status, created_at)
   - screen_submissions(id, developer_id, repo_url, submitted_at, decision, notes)
   
   Screens: /login, /projects/new, /projects/[id] (the three matches), /apply (developers), /admin/review.
   Env vars (names only): NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY (server only), OPENAI_API_KEY, RESEND_API_KEY.
   
   Do not build: billing, sprint packages, escrow or payouts, Clerk, a public developer directory, testimonials.
   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 VibeCoders: a quick, explainable match for a founder, and a vetting step that is real.
   1. The founder form takes a project name, a description, a preferred stack (Next.js, React, Python, Node, Supabase or other), a timeline (this week, 2 weeks or ongoing) and a budget range.
   2. Send the description to the OpenAI API with a strict JSON schema { required_skills: string[], complexity: "low" | "medium" | "high", recommended_ai_tools: string[] }. Keep only values that appear in a fixed skills list and a fixed tools list in one file.
   3. Match in code: among developers with status active, score by the overlap between the project's required skills and the developer's stack. Rank rated developers (sprint_rating of 4.2 or more) first, then unrated ones shown as "new, not yet rated". Show the top 3 as cards with top skills, tools, rating and a Request Sprint button.
   4. Request Sprint creates a match and emails the developer through Resend. The developer accepts or declines on their dashboard.
   5. A developer applies with a GitHub address, a sample project and an optional Loom link, then receives the take-home task by email: a 90-minute task to build a Next.js page showing a sorted leaderboard from a mock table, submitted as a repository address.
   6. /admin/review (admin only) lists applications with the GitHub link, the video and the submission. Approve sets the developer active and sends a welcome email. Reject sends a polite email.
   Rules: never state a speed multiple or a trust claim you cannot support. Show the reason for each match (the skills that overlapped).
   Empty state: with no active developers, tell the founder the roster is opening soon and offer to be emailed.
   Done when: a sample project returns 3 developers ranked by overlap with the matching skills shown, a developer outside the lists is not matched, Request Sprint sends one email, and an approved applicant appears in matches.

3. 3. Landing Page

   Build a one-page landing site for VibeCoders, a vetted roster of developers who build with AI tools.
   Hero: "Ship your MVP this week." Sub: "Developers who build with Cursor, Claude and similar tools, vetted with a real take-home task." Two buttons: Join the waitlist as a founder, Apply as a developer.
   Sections: how it works in three steps (post a project, get matched, sprint together), a developer card grid with three placeholder cards (name, top skill, tools, rating), a placeholder for founder testimonials to replace with real ones, and an FAQ on how developers are vetted and what a sprint is.
   Waitlist: store the email and the role in a waitlist table in Supabase. No other service.
   Style: Geist, a dark background, one lime accent, no illustrations.
   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 VibeCoders: a wordmark and a monogram that read as technical and energetic, clear at 16 pixels, such as a "VC" with a small bolt.
   Colors: black (#0A0A0A), electric lime (#AEFF00) and warm white (#FAFAF7). Type: a geometric mono for brand marks and Geist for body text.
   Deliverables: wordmark, monogram, a developer card layout, a Tailwind color and font config, and a one-paragraph voice guide.
   Done when: each deliverable is saved in one folder and the monogram is readable at 16 pixels.