Claude Code Prompts for SaaS MVPs

An MVP is not a small product — it's an experiment wrapped in the smallest product that can run it. These prompts enforce that order: cut scope before writing code, scaffold the boring-but-critical parts (auth, billing, tenant isolation) in one shot, and harden only what a first-time visitor would actually see. The sequence matters: Scope Cutter → Scaffold → Schema → Copy → Seed → Hardening.

I will describe a product idea. Before writing any code, return: (1) the single core user journey in 5 steps or fewer; (2) a feature cut-list — everything NOT needed for launch, each with a one-line reason it can wait; (3) the riskiest assumption the MVP must test; (4) a 2-week build plan where each day ends in something demoable. Challenge my scope aggressively; if a feature does not serve the core journey or the riskiest assumption, cut it.

Scaffold a minimal SaaS with Next.js (App Router, TypeScript, Tailwind). Requirements: (1) Supabase auth (email magic link); (2) a protected /app page that reads the session server-side; (3) Stripe Checkout with one $9/mo plan, webhook handler that flips users.paid in Supabase; (4) a landing page with hero, 3 benefits, pricing, FAQ. Generate clean file-by-file, no placeholder comments, every file complete and runnable. Explain nothing except choices you had to make.

Design the Supabase/Postgres schema for this app: <describe app>. Deliver: (1) tables with columns, types and FKs; (2) row-level-security policies for 'users see only their own data' on every table, written as actual SQL; (3) indexes for the 3 most likely query patterns; (4) what you deliberately did NOT normalize and why. Flag any table where a wrong RLS policy would leak data across tenants.

Write landing page copy for <product> targeting <audience>. Structure: (1) headline under 10 words stating the outcome, not the technology; (2) subheadline handling the #1 objection; (3) 3 benefit blocks in 'verb the outcome' form, no jargon; (4) 5 FAQ questions that are actually objections in disguise, with answers; (5) one CTA line repeated at top and bottom. Tone: plain English a smart 12-year-old understands. No hype words like revolutionary, game-changing, unleash.

Generate seed data for this schema: <schema>. Include: 2 normal rows per table; then 1 row each for the edge cases — empty optional fields, unicode names, 10KB text field, dates at min/max bounds, a soft-deleted row, and a row that violates no constraint but 'looks wrong' to a human. Explain in one line per edge row what UI bug it is designed to expose.

Audit this codebase as if we launch tomorrow. Report only, no fixes yet: (1) every place an unhandled error reaches the user as a crash or blank page; (2) missing input validation on any write path; (3) obvious N+1 or missing-index queries on list endpoints; (4) any secret that could leak client-side; (5) the 3 fixes I should do before launch and the 3 that can wait a week. Rank by 'how bad it looks to a first-time visitor'.