flow-patterns
Flow Patterns
How a product feels over time, not just in a single frame.
How to use
/flow-patternsApply flow design constraints to this conversation.
Constraints
Flow Principles
- MUST ensure the user can answer at any point: where am I, where did I come from, what happens next?
- MUST use the minimum number of steps for the complexity of the action. Not zero steps. The right number.
- MUST design error recovery as part of the flow, not an afterthought
- SHOULD prefer undo over confirmation ("Action completed. Undo?" beats "Are you sure?")
Progressive Disclosure
- MUST show only what's needed now and reveal complexity on demand
- MUST decide at what point "simple" becomes "hiding things"
- SHOULD use contextual actions (show actions where the content is, not in a distant toolbar)
- SHOULD use smart defaults (pre-fill based on context, set the most common option)
Anti-Patterns
- Multi-step flows with no progress indicator
- Asking for information you could have inferred from context
- Dead-end error states with no recovery path
- Mandatory steps that aren't actually required
- Confirmation dialogs for easily reversible actions
More from dragoon0x/taste-skills
visual-audit
The 10-second design audit. Look at any design and name what's working and what's not within seconds. Trains rapid pattern recognition for hierarchy, spacing, type, and color. Use when evaluating designs quickly, giving first-impression feedback, or building perception speed.
19motion-design
Animation as communication. Feedback, orientation, emphasis, delight. If motion doesn't serve one of these four purposes, it shouldn't exist. Use when evaluating animation quality, designing transitions, or deciding whether motion adds or subtracts.
15taste-as-strategy
Use taste as a competitive moat and business advantage. In the AI and vibe-coding era, execution is commoditized. Taste is the defensible edge. Use when advising founders on product differentiation, building product culture, evaluating why some products win despite fewer features, or understanding taste as a strategic asset.
15teaching-taste
Help other designers develop judgment without imposing your style. Use when mentoring designers, running design education, or building team-wide quality standards.
15tradeoff-assessment
Name what was prioritized, what was sacrificed, and whether the tradeoff was right. Every design decision trades something. Use when evaluating design decisions, defending choices, or helping teams understand what they're giving up.
14field-notes
Structured taste breakdowns of real products. The format for making taste observations legible and shareable. Use when analyzing products, writing case studies, documenting design observations, or teaching through example.
14