
User Flow Diagram
When you need to map out how users move through your product, this creates clean flow diagrams with proper notation for screens, decisions, branches, and error paths. It knows the difference between task flows (single linear path), user flows (multiple branches), and wire flows (with wireframe thumbnails), and pushes you to start with the happy path before layering in edge cases. The annotations cover decision criteria, system actions, and async processes, which means you're not just getting boxes and arrows but actually useful documentation. It enforces consistent labeling on every connector, so six months from now someone can actually follow what you built.
- install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.
- 10
- skills.sh installs
- 2.7K
- GitHub stars
- 3.3K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add owl-listener/designer-skills --skill user-flow-diagram --agent claude-codeInstalls into .claude/skills of the current project.
Files
User Flow Diagram
You are an expert in creating clear user flow diagrams that map paths through a product.
What You Do
You create flow diagrams showing how users move through a product to accomplish goals, including decisions, branches, and error paths.
Flow Diagram Elements
- Entry point: Where the user enters the flow (circle/oval)
- Screen/page: A view the user sees (rectangle)
- Decision: A branching point (diamond)
- Action: Something the user does (rounded rectangle)
- System process: Backend operation (rectangle with side bars)
- End point: Flow completion (circle with border)
- Connector: Arrow showing direction of flow
Flow Types
- Task flow: Single path for a specific task (linear)
- User flow: Multiple paths based on user type or choice
- Wire flow: Flow combined with wireframe thumbnails
Creating Effective Flows
- Define the goal the flow accomplishes
- Identify the entry point(s)
- Map the happy path first
- Add decision points and branches
- Map error paths and recovery
- Mark exit points
- Note system actions happening in background
Flow Annotations
- Screen names and key content
Sponsors
Details
- Repository
- github.com/owl-listener/designer-skills
- Category
- Git & Pull Requests
- First seen
- Jun 3, 2026
More from owl-listener/designer-skills
All 68- Icon System2.6K
- Layout Grid2.6K
- Heuristic Evaluation2.6K
- Data Visualization2.6K
- Spacing System2.5K
- Responsive Design2.5K
- Wireframe Spec2.5K
- Micro Interaction Spec2.5K
- Loading States2.5K
- Animation Principles2.5K
- Design Critique2.5K
- Design Qa Checklist2.5K
- Design Token Audit2.5K
- State Machine2.4K
- Error Handling Ux2.4K
- Design Token2.4K
- Usability Test Plan2.4K
- Accessibility Audit2.4K
- Case Study2.4K
- Ux Writing2.4K
- Journey Map2.4K
- Component Spec2.4K
- Design Principles2.4K
- Theming System2.4K