Get Agent Loadout
Vibe codingIntermediateDocs-checked, not yet hands-on tested

Ship a vibe-coded SaaS MVP

Go from idea to a paid, deployed web app with auth, a database and checkout.

Starter prompt

Read PLAN.md. Build the smallest version of this SaaS that a stranger could pay for: email login (Supabase Auth), one core feature, a Stripe Checkout page for a single monthly plan, and a settings page. Use Row Level Security on every table. Before writing code, list the tables and RLS policies and wait for my OK. After each step, run the app and tell me exactly what to click to test it.

Config

.mcp.json

{
  "mcpServers": {
    "supabase": { "type": "http", "url": "https://mcp.supabase.com/mcp?project_ref=YOUR_PROJECT_REF" },
    "vercel":   { "type": "http", "url": "https://mcp.vercel.com" },
    "stripe":   { "type": "http", "url": "https://mcp.stripe.com" }
  }
}

Setup steps

  1. Write a one-page PLAN.md: who it's for, the one feature, the price.
  2. Create a Supabase project and a Vercel project; add the three MCP servers and authenticate each with /mcp.
  3. Run the starter prompt in Claude Code and approve the schema first.
  4. Deploy a preview on Vercel, test checkout in Stripe test mode, then switch to live keys.

Why this works

Claude Code can read your schema, deploy and inspect Stripe objects through official MCP servers, so it can check its own work instead of guessing.

Watch out

Point the Supabase MCP at a development project, not production. Add read_only=true to the URL when you only need it to inspect data.

Related loadouts

Compare the gear: AI coding agents tier list · AI code review tier list