ss-flow

# UX Flow Designer ## When NOT to use - For implementing a single page → use `/ss-page` after the flow is settled - For copy on each step → use `/ss-copy` after the structure is settled - For information architecture of an entire product — narrow scope to one flow first - For high-fidelity mockups — this produces a flow map, not pixel-perfect designs Design a user flow: **$0** Description: $ARGUMENTS ## Instructions 1. Read the design system reference: - `CLAUDE.md` for component inventory - `DESIGN-LANGUAGE.md` for layout patterns (sections 13-14, 19-20) - `components/patterns/` for available building blocks 2. Apply these UX principles: ### Information Architecture - **Progressive Disclosure**: Show only what's needed at each step. Hide complexity behind logical drill-downs. - **Miller's Law**: Chunk information into groups of 5-9 items maximum. - **Hick's Law**: Minimize choices per screen. Fewer options = faster decisions. ### Navigation Patterns - **Hub & Spoke**: Dashboard → detail pages → back to dashboard (default for mobile apps) - **Linear Flow**: Step 1 → Step 2 → Step 3 (for forms, onboarding, checkout) - **Tab Navigation**: 3-5 top-level sections via BottomNav ### Screen Flow Rules - Every flow must have a **clear entry point** and **clear exit point** - Maximum **3 taps** to reach any key feature from the home screen - Back navigation must always be available (except root screens) - Error states must provide **recovery paths** (retry, go back, ...