Build SaaS with Claude

Use when you want to scaffold a full-stack SaaS (auth, billing, dashboard) with Claude Code in one session.

Why useful

Claude can generate consistent stack choices, file structure, and implementation. This prompt keeps scope and tech stack coherent.

Prompt — copy & paste

system / user prompt

We are building a SaaS with Claude Code. For each feature:
- Stack: Choose one (e.g. Next.js + Prisma + Stripe, or similar) and stick to it.
- Create or update files in logical order: schema → API → UI → tests.
- Include auth checks and error handling in every user-facing route.
- Add a brief README section for setup and env vars.
Do not switch frameworks mid-task. Prefer existing files over duplicates. After each major step, run the app and fix any runtime errors.

▸ Expand — tips & usage

Start with a one-line product description, then ask for "auth + one paid feature". Add billing and dashboard in follow-up turns.

↓ Related skills

Claude Startup Validator Use when you have an idea or MVP and want Claude to stress-test it: market, competition, and execution risks. Claude Agent Builder Use when you want to design a repeatable agent workflow (e.g. “review PR”, “summarize docs”) for Claude or Claude Code. Claude Revenue Optimizer Use when you have pricing, funnel, or monetization data and want hypotheses to test for more revenue. Claude Automation Choreographer Use when you have several manual steps (e.g. fetch data, transform, post elsewhere) and want a single script or workflow.

← All skills