How do I install the Ss Flow skill?

Run npx skillmds@latest add bitjaru/ss-flow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Ss Flow skill do?

Design user flows and navigation structure following proven UX patterns It is listed under Coding & Dev Tools on SkillMD.

Is Ss Flow safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ss Flow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ss Flow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ss Flow?

bitjaru (@bitjaru) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ss Flow by bitjaru — Agent Skill

Name: Ss Flow
Rating: 4.2 (5 reviews)
Author: bitjaru

File contents

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

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
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 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)
Navigation: use the resolved surface adapter; BottomNav is only one possible mobile pattern.

Screen Flow Rules

Every flow must have a clear entry point and clear exit point
Key features should be reachable with an appropriate number of steps for the product and platform; do not impose a universal tap count.
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 selected output grammar's information hierarchy; do not impose a Hero → KPI Grid → Details → Lists template on unrelated products.
Each screen should answer ONE primary question when the task calls for it.
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 primitives selected by the artifact's adapter and grammar
Generate the actual page files using /ss-page conventions.

---name: ss-flowdescription: Design user flows and navigation structure following proven UX patterns--- # 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 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) - **Navigation**: use the resolved surface adapter; BottomNav is only one possible mobile pattern. ### Screen Flow Rules - Every flow must have a **clear entry point** and **clear exit point** - Key features should be reachable with an appropriate number of steps for the product and platform; do not impose a universal tap count. - 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 selected output grammar's information hierarchy; do not impose a Hero → KPI Grid → Details → Lists template on unrelated products. - Each screen should answer ONE primary question when the task calls for it. - Above the fold: the most important metric or action - Use the 4 section types: Full Card (A), Grid (B), Carousel (C), Hero (D) 3. 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 primitives selected by the artifact's adapter and grammar 4. Generate the actual page files using `/ss-page` conventions.

Frequently asked questions

Ss Flow