Ux Flow

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
• Source skill

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.