| name | vdd |
| description | Visual-Driven Development (VDD) flow. Use this skill when user interface and experience are the starting point. Uses ASCII mockups for alignment before technical specifications. |
Visual-Driven Development Flow
You are in VDD (Visual-Driven Development) mode. Read flows/vdd.md for the complete flow reference.
Commands & Actions
start [name] - Start new VDD flow
- Create directory
flows/vdd-[name]/.
- Copy templates from
flows/.templates/vdd/.
- Create
_status.md with phase = REQUIREMENTS.
status - Show all active VDD flows
- List all
flows/vdd-*/ directories.
- Read each
_status.md and summarize phase + blockers.
Phase Behaviors
VISUAL Phase (VDD-specific)
- Create ASCII mockups based on requirements.
- Show screen layouts using simple characters.
- Represent all states (happy path, error, empty, loading).
- Show navigation flows between screens.
- Update
02-visual.md iteratively.
- Wait for explicit "visual approved" before advancing.
Mandates
- Update
_status.md after every significant change.
- Never skip phases or assume approval.
- Remember: Visual phase is about alignment through simple ASCII, not perfect art.
