SpecFlow
The brief
For people who can't speak design: a conversation that ends with a working app.
Coding agents can build almost anything, if you can describe what it should look and feel like. Most people can’t put taste into words.
What I built
A design-brief generator for the coding-agent era: a short interview, what are we building, what should it feel like, which motions, what’s the one action a visitor should take, answered by choosing from real options instead of describing them. SpecFlow turns that into a design.md and a code.md that Claude Code, Cursor or v0 can build from directly.
Feel, chosen from real options
Named palettes replace design vocabulary. You pick what looks right instead of describing it.
Motion you can preview, not imagine
Entrance, scroll, hover and text effects play live before you commit: a motion vocabulary with previews instead of adjectives.
Two files a coding agent can execute
The interview ends in design.md and code.md: a design-system spec plus an implementation brief that Claude Code, Cursor or v0 can build from directly.
An interview, not a questionnaire
What are we building, what should it feel like, what's the one action a visitor should take: short questions, concrete choices, a working brief at the end.
The hard part
Turning taste into a machine-readable spec: a curated palette library; a motion vocabulary: entrance, scroll, hover, page transitions, micro-interactions, text effects, with live previews; and an exporter that emits a design-system spec plus an implementation brief as two separate markdown files.
The result
Taste becomes a machine-readable spec: two markdown files a coding agent can execute without guessing.
Taste becomes a machine-readable spec.
Two markdown files a coding agent can execute without guessing.
Real options replace design vocabulary.
