The Mini-PRD
Before typing your first prompt, spend 10 minutes writing a one-page spec. This document will be your north star and Claude's instruction manual.
The Template
# [Project Name] ## What It Is [1-2 sentences describing the product] ## Who It's For [Target user in one sentence] ## Core Features (MVP) 1. [Feature 1] 2. [Feature 2] 3. [Feature 3] (Keep it to 3-5 features max) ## Nice to Have (Post-MVP) - [Future feature 1] - [Future feature 2] ## Design Notes - [Visual style preferences] - [Color scheme] - [Any specific inspiration] ## Technical Decisions - Framework: [e.g., Next.js, vanilla HTML] - Styling: [e.g., Tailwind CSS] - Data: [e.g., localStorage, no backend] ## Definition of Done I'll consider this done when: - [ ] [Criterion 1] - [ ] [Criterion 2] - [ ] [Criterion 3]
Example: Pomodoro Timer
## What It Is
A simple timer that follows the Pomodoro technique — 25-minute work sessions with 5-minute breaks.
## Who It's For
Me, to stay focused during deep work sessions.
## Core Features (MVP)
1. Start/pause/reset timer
2. Visual countdown display
3. Sound alert when timer ends
4. Auto-switch between work and break modes
## Design Notes
- Dark mode with accent colors (red for work, green for break)
- Big, readable timer numbers
- Minimal UI, no distractions
## Technical Decisions
- Framework: React (single page)
- Styling: Tailwind CSS
- Data: useState only (no persistence needed)
## Definition of Done
- [ ] Timer counts down from 25:00
- [ ] Button to start/pause works
- [ ] Makes sound when reaching 00:00
- [ ] Deployed to Vercel with real URL
Why This Works
Forces Clarity
Writing it down reveals gaps in your thinking before you start building.
Prevents Scope Creep
When you're tempted to add features, check: is it in the MVP list?
Perfect for Claude
You can paste this spec directly to Claude as your opening prompt.
📝 Action Item
Write your 1-page spec now. Don't overthink it — you can revise as you go. The act of writing it is more valuable than getting it perfect.