v0.dev PRD Generator (Pro Ver.)

Overview

This prompt lets product leaders feed v0.dev a fully structured PRD and receive a multi-file, auto-modular Next.js 19 scaffold in return. v0.dev breaks the code into bite-sized files (app/, components/, hooks/, lib/, tests/, Tailwind theme, etc.), each capped at 100 LOC and marked with #file directives so you can paste the output straight into a repo. After generation, v0.dev may display a simple pop-up asking to integrate your Supabase project. When prompted, just follow the in-app guidance to connect your live backend. This prompt is built for teams who need a fast, practical way to move from intention to execution.

In a delivery context, this prompt helps you align stakeholders, surface the right constraints, and structure the output so it is immediately actionable.

Prompt template

As **Head of Product**, you're creating a world-class **Product Requirements Document (PRD)** that will guide v0.dev to output a clean, multi-file Next.js project.

- I provide a lightweight template; you fill the blanks in plain sentences.
- v0.dev must infer the optimal folder layout and emit `#file` directives on its own, keeping each file , I want  so that ."

4. **Functional Requirements** — Group > Feature : description | priority (P0/P1).

5. **User Experience**
   - Entry & Onboarding (first-time flow)
   - Core Flow (step-by-step with Tailwind + shadcn/ui)
   - Advanced & Edge Cases

6. **Prompt Library** — 3-5 copy-paste snippets for v0.dev (e.g., "Create a task list with checkbox transitions.").

7. **Code Structure (AI-Generated)**
   - You, the AI, MUST decide file breakdown and emit `#file` directives automatically (app/page.tsx, components/*.tsx, hooks/, lib/, styles/, tests/...).
   - Ensure separation of concerns and add brief comments atop each file explaining its purpose.

8. **Narrative** — 200-300 characters: user pain > solution > outcome.

9. **Success Metrics** — User, Business, Tech, Code-Productivity (e.g., "v0 prompt > PR merge

How to use this prompt

• State the objective and the product context in one sentence.
• Add any constraints such as timeline, target users, or business metrics.
• Ask for a structured output (framework, checklist, or decision summary).

Prompt details