The Master Prompt I Use to Generate a Full SaaS Blueprint (7 Sections)

Most teams lose momentum before coding because setup is inconsistent: ad-hoc prompts, missing architecture details, and manual reformatting into project docs.

This master prompt solves that by forcing one strict 7-section blueprint contract. You get artifacts you can copy directly into planning docs, Cursor tasks, and implementation PRs.

• A complete output every time: prompt, stack, architecture, implementation plan, CLAUDE.md, .cursorrules, and launch gotchas.
• Concrete artifacts only: folder tree, DB schema snippet, API contract snippet, testing strategy, MVP vs V2 split.
• Better handoff quality between founder, PM, and engineering without rewriting content.

Paste this prompt as your base and only replace the input block. Keep the quality gates unchanged so output stays consistent across providers.

Role: You are a principal product engineer.

Goal:
Turn the input idea into a complete 7-section implementation blueprint.

Output contract:
1) Master Prompt for Claude/Cursor/Codex
2) Recommended Tech Stack
3) Architecture & Data Model
4) Step-by-Step Implementation Plan
5) CLAUDE.md File
6) .cursorrules File
7) Gotchas & Pro Tips

Hard requirements:
- Include at least one DB schema snippet (SQL or Prisma-like).
- Include at least one API contract snippet (REST or tRPC style).
- Include explicit testing strategy (unit/integration/e2e).
- Include an MVP scope vs V2 scope list.
- No generic fluff. Every recommendation must map to files, endpoints, tables, jobs, or tests.

### INPUT ###
Idea: <replace>
Required scope constraints (MUST include):
- <replace with mandatory labels/scope>
### END INPUT ###

Try it now in the generator: vibemeta.app

Keep the idea short and specific. Use labels only for requirements that are truly mandatory. If you add too many soft preferences, quality drops and sections become generic.

Idea:
Build a multi-tenant invoice SaaS for agencies with quote-to-invoice flow, Stripe billing, overdue reminders, and accountant exports.

Required scope constraints (MUST include):
- Auth with organization-level RBAC
- Stripe subscriptions + webhook reconciliation
- Audit log for invoice state changes
- CSV export for accounting
- Admin support dashboard

Before implementation, run this checklist. It catches most low-quality outputs without another full generation.

• All 7 section headings exist exactly once and in order.
• Architecture includes a realistic folder tree and trust boundaries.
• Data model includes indexes for hot paths and uniqueness constraints.
• API contracts include request/response examples and failure cases.
• Implementation plan includes phases with acceptance criteria.
• Gotchas include security, privacy, reliability, and launch risks.

Do not regenerate from zero immediately. Ask for targeted repairs section by section. This preserves good parts and saves time.

Repair prompt #1:
"Rewrite section 3 only. Keep existing stack. Add missing DB indexes, one API contract with error responses, and explicit tenancy constraints."

Repair prompt #2:
"Rewrite section 4 only. Keep current architecture. Add phase acceptance criteria and 2 mini-prompts per phase for Cursor implementation."

Repair prompt #3:
"Rewrite section 7 only. Add 12 concrete launch risks (security, retries, webhooks, data retention, quotas)."

Use the blueprint as execution source of truth. Implement phase by phase, commit after each acceptance criterion, and avoid parallel feature drift.

• Create one issue per phase with acceptance criteria copied from section 4.
• Add CLAUDE.md and .cursorrules before starting coding sessions.
• Ship MVP first, then schedule V2 items as explicit backlog tasks.
• After each merged phase, refresh blueprint notes with real implementation deltas.