v0.dev PRD Generator (Pro Ver.)

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 < 100 LOC and isolating state from UI.
• Follow best practices: `app/`, `components/`, `hooks/`, `lib/`, tests, and Tailwind/theme setup.

[Press Enter]

## PRD Structure (v0.dev-Optimized, Auto-Modular)

1. 🧭 **tl;dr** – 2-3 sentences on problem, solution, main benefit, target user.

2. 🎯 **Goals**
• **Business Goals** (3-5 SMART)
• **User Goals** (3-5 clear benefits)
• **Non-Goals** (2-3 out-of-scope items)

3. 👥 **User Stories** – “As a [persona], I want [action] so that [benefit].”

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 < 2 h”).

10. ⚙️ **Technical Considerations**
• Default Stack = Next.js 19 (App Router) + Tailwind v4 + shadcn/ui
• Backend & Auth = Supabase + Drizzle | Clerk
• Performance & QA = lazy-load, a11y, Playwright smoke tests, AI diff-review policy

11. 🔗 **Integration Points** – External services (e.g., Google Calendar, Slack).

[Press Enter]

>> **Fill only the items below; plain sentences, no special syntax.**

1. **Project Name**
2. **One-line tl;dr**
3. **Top Business Goals**
4. **Top User Goals**
5. **Key Non-Goals**
6. **Main Personas & User Stories**
7. **Must-have Features**
8. **Tech-stack Preferences** (if different)
9. **Most-critical Success Metric**
10. **External Integrations**

────────────────────────────────────────

### ✨ Example filled for a simple to-do web-app (delete or adapt)

1. **Project Name**
 “SimpleTodo”

2. **One-line tl;dr**
 “A minimal web app that lets users create, organise, and track personal tasks across devices.”

3. **Top Business Goal** *(plus 2-4 more)*
e “Ship MVP in four weeks and reach 30 % seven-day retention within the first month.”

4. **Top User Goal** *(plus 2-4 more)*
 “Add a new task in under five seconds from any screen.”

5. **Key Non-Goal** *(plus 1-2 more)*
 “Real-time multiplayer collaboration is out of scope for the initial release.”

6. **Main Personas & their User Stories**

• Busy Professional ▸ “As a busy professional, I want keyboard shortcuts to add tasks quickly so that I don’t break focus.”
• Student ▸ “As a student, I want due-date reminders so that I never miss an assignment.”

7. **Must-have Features** *(group > feature | priority)*

Core    > TaskCreate       | P0  
Core    > TaskList         | P0 
Core    > TaskComplete     | P0 
Enhance > DueDateReminder  | P1

8. **Any Technical Stack preferences** *(if different)*
 “Use React 19 with TanStack Query for data fetching.”

9. **Success Metric you care most about**
 “Average task-completion rate ≥ 60 % within 24 hours.”

10. **External Integrations**
 “Google Calendar, Slack notifications”