Ss Flow
Design user flows and navigation structure following proven UX patterns
Install
$ agentstack add skill-bitjaru-styleseed-ss-flow ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-bitjaru-styleseed-ss-flow) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: bitjaru
- Source: bitjaru/styleseed
- License: MIT
- Homepage: https://styleseed-demo.vercel.app
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.