ux-flow-diagram
[UI/UX] Visualizes user flows and screen transitions as ASCII diagrams. Represents navigation flows, user journeys, and screen-to-screen paths. Use when requesting 'flow diagram', 'user journey visualization', or 'navigation flow'.
When & Why to Use This Skill
This Claude skill enables the generation of professional ASCII-based UX flow diagrams to visualize user journeys and screen transitions. It streamlines the design process by providing a text-based way to map out navigation paths, conditional logic, and interface hierarchies, making it an essential tool for UI/UX designers, product managers, and developers seeking clear architectural documentation.
Use Cases
- Documenting User Journeys: Create step-by-step visual representations of user interactions to identify and optimize the end-to-end experience.
- Designing Navigation Flows: Map out the structural connections and transitions between different screens or pages in a web or mobile application.
- Defining Feature Logic: Use specialized ASCII symbols for decisions and processes to represent complex conditional branching and exception handling.
- Rapid Prototyping & Communication: Quickly generate and share flowcharts during brainstorming sessions to align stakeholders on product logic without needing external design tools.
| name | ux-flow-diagram |
|---|---|
| description | "[UI/UX] Visualizes user flows and screen transitions as ASCII diagrams. Represents navigation flows, user journeys, and screen-to-screen paths. Use when requesting 'flow diagram', 'user journey visualization', or 'navigation flow'." |
UX Flow Diagram
A skill that visualizes user flows and screen transitions as ASCII diagrams.
When to Use
- Documenting user journeys
- Designing navigation flows between screens
- Defining user flows per feature
- Representing conditional branching and exception handling flows
Flow Diagram Symbols
Basic Nodes
┌─────────┐
│ Screen │ ← Screen/Page
└─────────┘
╔═════════╗
║ Screen ║ ← Start/End screen (emphasis)
╚═════════╝
((Action)) ← User action
<Decision?> ← Condition/Branch point
[Process] ← System process
Connection Lines
───→ Unidirectional flow
←──→ Bidirectional flow
- - → Optional/conditional flow
═══→ Main flow (emphasis)
Flow Patterns
Linear Flow (Sequential)
╔═══════════╗ ┌───────────┐ ╔═══════════╗
║ Start ║───→│ Step 1 │───→║ End ║
╚═══════════╝ └───────────┘ ╚═══════════╝
Branching Flow
Yes ┌───────────┐
┌────────→│ Path A │────┐
┌───────────┐ │ └───────────┘ │ ┌───────────┐
│ Screen │───→<Decision?> ├───→│ Result │
└───────────┘ │ ┌───────────┐ │ └───────────┘
└────────→│ Path B │────┘
No └───────────┘
Constraints
- Flows progress left-to-right, top-to-bottom
- Complex flows should be split into sub-flows
- All branch points need clear condition labels