# README Template for Generated Projects

Use this exact structure when generating README.md files in Phase 4.

```markdown
# [name]

**[One-liner pitch — under 120 chars]**

[1-2 sentences for someone with 5 seconds to decide if they care]

## Demo

[Describe exactly what GIF/screenshot to capture. Be specific:
"Record a 15-second GIF showing: paste a URL → watch it extract
the recipe → output a meal plan. The 'wow' moment is when it
generates the shopping list grouped by store aisle."]

## Install

\`\`\`bash
[One command. If it needs more than one, simplify the tool.]
\`\`\`

## Usage

\`\`\`bash
# Simple case
[example 1]

# Power-user case
[example 2]

# Surprising case — show range
[example 3]
\`\`\`

## Why This Exists

[2-3 sentences. Tie to the pain point. "I got tired of..."
or "Every time I tried to X, I had to Y. So I built this."]

## How It Works

[3-5 sentences. Just enough to build trust, not a whitepaper.]

## Compatible With

[List platforms/environments]

## License

MIT
```

## Key Rules
- Hook in the FIRST LINE — no "Welcome to..."
- One-command install or the tool is too complex
- 3 examples that show range (simple, power-user, surprising)
- "Why this exists" creates empathy — relatable frustration
- No walls of text. Scannable. Tables over paragraphs.