$npx -y skills add bitjaru/styleseed --skill ss-flowDesign user flows and navigation structure following proven UX patterns
| 1 | # UX Flow Designer |
| 2 | |
| 3 | ## When NOT to use |
| 4 | |
| 5 | - For implementing a single page → use `/ss-page` after the flow is settled |
| 6 | - For copy on each step → use `/ss-copy` after the structure is settled |
| 7 | - For information architecture of an entire product — narrow scope to one flow first |
| 8 | - For high-fidelity mockups — this produces a flow map, not pixel-perfect designs |
| 9 | |
| 10 | Design a user flow: **$0** |
| 11 | Description: $ARGUMENTS |
| 12 | |
| 13 | ## Instructions |
| 14 | |
| 15 | 1. Read the design system reference: |
| 16 | - `CLAUDE.md` for component inventory |
| 17 | - `DESIGN-LANGUAGE.md` for layout patterns (sections 13-14, 19-20) |
| 18 | - `components/patterns/` for available building blocks |
| 19 | |
| 20 | 2. Apply these UX principles: |
| 21 | |
| 22 | ### Information Architecture |
| 23 | - **Progressive Disclosure**: Show only what's needed at each step. Hide complexity behind logical drill-downs. |
| 24 | - **Miller's Law**: Chunk information into groups of 5-9 items maximum. |
| 25 | - **Hick's Law**: Minimize choices per screen. Fewer options = faster decisions. |
| 26 | |
| 27 | ### Navigation Patterns |
| 28 | - **Hub & Spoke**: Dashboard → detail pages → back to dashboard (default for mobile apps) |
| 29 | - **Linear Flow**: Step 1 → Step 2 → Step 3 (for forms, onboarding, checkout) |
| 30 | - **Tab Navigation**: 3-5 top-level sections via BottomNav |
| 31 | |
| 32 | ### Screen Flow Rules |
| 33 | - Every flow must have a **clear entry point** and **clear exit point** |
| 34 | - Maximum **3 taps** to reach any key feature from the home screen |
| 35 | - Back navigation must always be available (except root screens) |
| 36 | - Error states must provide **recovery paths** (retry, go back, contact support) |
| 37 | - Loading states must use skeleton screens (never spinners in cards) |
| 38 | |
| 39 | ### Page Composition (from DESIGN-LANGUAGE.md) |
| 40 | - Follow the **Information Pyramid**: Hero → KPI Grid → Details → Lists |
| 41 | - Each screen should answer ONE primary question |
| 42 | - Above the fold: the most important metric or action |
| 43 | - Use the 4 section types: Full Card (A), Grid (B), Carousel (C), Hero (D) |
| 44 | |
| 45 | 3. Output format: |
| 46 | - **Flow diagram** in ASCII showing screen connections |
| 47 | - **Screen inventory** listing each screen's purpose and key components |
| 48 | - **Edge cases** (empty states, errors, loading) for each screen |
| 49 | - **Scaffolded pages** using `PageShell`, `TopBar`, `BottomNav` patterns |
| 50 | |
| 51 | 4. Generate the actual page files using `/ss-page` conventions. |