agent product skill risk: low
StyleSeed UX Flow Designer
Designs user flows and screen structures using StyleSeed UX patterns such as progressive disclosure, hub-and-spoke navigation, and information pyramids. Outputs an ASCII flow diagr…
SKILL 1 file
SKILL.md
--- name: ux-flow description: "Design user flows and screen structure using StyleSeed UX patterns such as progressive disclosure, hub-and-spoke navigation, and information pyramids." --- # UX Flow ## Overview Part of [StyleSeed](https://github.com/bitjaru/styleseed), this skill designs flows before screens. It uses proven UX patterns to define entry points, exits, screen inventory, and navigation structure so the implementation has a coherent user journey instead of a pile of disconnected pages. ## When to Use - Use when planning onboarding, checkout, account management, dashboards, or drill-down flows - Use when a new feature spans multiple screens or modal states - Use when users need a clear path through a task instead of a single isolated page - Use when the UI needs navigation logic before components are built ## How It Works ### Information Architecture Principles - progressive disclosure: reveal complexity only when needed - Miller's Law: chunk content into manageable groups - Hick's Law: minimize decision overload on each screen ### Common Navigation Models - hub and spoke for dashboards and detail views - linear flow for onboarding, forms, and checkout - tab navigation for 3 to 5 top-level areas ### Flow Rules - every flow has a clear entry point - every flow has a clear exit or success condition - key features should usually be reachable within three taps from home - non-root screens need back navigation - loading, empty, and error states need explicit recovery paths ## Output Provide: 1. An ASCII flow diagram 2. A screen inventory with each screen's purpose 3. Edge cases for loading, empty, and error states 4. Recommended page scaffolds and reusable patterns to implement next ## Best Practices - Optimize for clarity before density - Let one screen answer one primary question - Keep escape hatches visible for risky or destructive steps - Define state transitions before drawing detailed layouts ## Additional Resources - [StyleSeed repository](https://github.com/bitjaru/styleseed) - [Source skill](https://github.com/bitjaru/styleseed/blob/main/seeds/toss/.claude/skills/ux-flow/SKILL.md) ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
REQUIRED CONTEXT
- feature or task requiring multi-screen flow (e.g. onboarding, checkout, dashboard)
ROLES & RULES
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
EXPECTED OUTPUT
- Format
- markdown
- Schema
- numbered_list · An ASCII flow diagram, A screen inventory with each screen's purpose, Edge cases for loading, empty, and error states, Recommended page scaffolds and reusable patterns to implement next
- Constraints
- include ASCII flow diagram
- include screen inventory with purpose
- include edge cases for loading/empty/error states
- include recommended page scaffolds and reusable patterns
SUCCESS CRITERIA
- Optimize for clarity before density
- Let one screen answer one primary question
- Keep escape hatches visible for risky or destructive steps
- Define state transitions before drawing detailed layouts
CAVEATS
- Missing context
- Specific user task or feature description to analyze
QUALITY
- OVERALL
- 0.85
- CLARITY
- 0.90
- SPECIFICITY
- 0.85
- REUSABILITY
- 0.90
- COMPLETENESS
- 0.80
IMPROVEMENT SUGGESTIONS
- Add an explicit 'Input' section describing the expected user-provided context (e.g., feature name, target users, constraints).
USAGE
Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.
MORE FOR AGENT
- Beachhead Market Segment Analyzeragentproduct
- UI/UX Design Intelligence Guideagentproduct
- Customer Journey Map Generatoragentproduct
- Agile User Stories Generator with 3Csagentproduct
- StyleSeed UX Flow Designeragentproduct
- New Product Feature Ideationagentproduct
- Existing Product Trio Idea Brainstormeragentproduct
- Onboarding CRO Flow Designeragentproduct
- StyleSeed UI Design Token Manageragentproduct
- Product Requirements Document Drafteragentproduct
- JTBD Job Stories Generatoragentproduct
- Product Feature Backlog Prioritizeragentproduct
- Research Data User Persona Creatoragentproduct
- StyleSeed UX Flow and Screen Designeragentproduct
- Turkish Car Valuation Platform Designeragentproduct
- Opportunity Solution Tree Product Discoveryagentproduct
- Product Launch Pre-Mortem Risk Analyzeragentproduct
- Niche Domain Intelligence Report Generatoragentproduct
- Impact Risk Assumption Prioritizeragentproduct
- StyleSeed UX Feedback Statesagentproduct
- Senior Product Manager Skills Agentagentproduct
- Prioritization Frameworks Reference Guideagentproduct
- Senior Product Manager Skills Agentagentproduct
- StyleSeed UX Feedback States Adderagentproduct
- Senior Product Manager Skills Agentagentproduct