Ss Flow
Designss-flowSs Flow is an Agent Skill for design published in the bitjaru/styleseed repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Design user flows and navigation structure following proven UX patterns
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/bitjaru/styleseed/blob/HEAD/engine/.claude/skills/ss-flow/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ss-flow, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
UX Flow Designer
When NOT to use
- For implementing a single page → use
/ss-pageafter the flow is settled - For copy on each step → use
/ss-copyafter 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
-
Read the design system reference:
CLAUDE.mdfor component inventoryDESIGN-LANGUAGE.mdfor layout patterns (sections 13-14, 19-20)components/patterns/for available building blocks
-
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, contact support)
- Loading states must use skeleton screens (never spinners in cards)
Page Composition (from DESIGN-LANGUAGE.md)
- Follow the Information Pyramid: Hero → KPI Grid → Details → Lists
- Each screen should answer ONE primary question
- Above the fold: the most important metric or action
- Use the 4 section types: Full Card (A), Grid (B), Carousel (C), Hero (D)
-
Output format:
- Flow diagram in ASCII showing screen connections
- Screen inventory listing each screen's purpose and key components
- Edge cases (empty states, errors, loading) for each screen
- Scaffolded pages using
PageShell,TopBar,BottomNavpatterns
-
Generate the actual page files using
/ss-pageconventions.