ss-flow

# UX Flow Designer ## Registry-first artifact boundary When `.styleseed/project.json` and `.styleseed/artifacts/index.json` exist, resolve the requested artifact ID first, then read only `.styleseed/bundles/<artifact-id>.md` and `.styleseed/manifests/<artifact-id>.json`. Never fall back to the global legacy bundle for a registry project. Legacy projects may use `.styleseed/effective-rules.md` only when no registry exists. ## 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. - **Cognitive load**: Chunk information around the user's decision; the resolved grammar and content density decide the grouping rather than a universal item count. - **Hick's Law**: Minimize choices per screen while preserving the product's real task vocabulary. ### Navigation Patter...