User Flow Diagram
Diagram screen-level paths, decision points, and branch logic. Use when specifying how a feature is traversed. For the emotional end-to-end arc, use `journey-map` (design-research).
Install
/plugin marketplace add Owl-Listener/designer-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Owl-Listener/designer-skills --skill user-flow-diagramgit clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/prototyping-testing/skills/user-flow-diagram ~/.claude/skills/user-flow-diagramPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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 1. Define the goal the flow accomplishes 2. Identify the entry point(s) 3. Map the happy path first 4. Add decision points and branches 5. Map error paths and recovery 6. Mark exit points 7. Note system actions happening in background ## Flow Annotations - Screen names and key content - Decision criteria at each branch - Error conditions and handling - System events and notifications - Time delays or async processes ## Best Practices - One flow per user goal - Start with happy path, then add complexity - Include error and edge case paths - Keep flows readable (not too many branches on one diagram)
Details
- Skill name
user-flow-diagram- Repository
- Owl-Listener/designer-skills
- Path
prototyping-testing/skills/user-flow-diagram/SKILL.md- License
- MIT
- Repo updated
- 5 September 2026
FAQ
What does the User Flow Diagram skill do?
Diagram screen-level paths, decision points, and branch logic. Use when specifying how a feature is traversed. For the emotional end-to-end arc, use `journey-map` (design-research).
How do I install the User Flow Diagram skill?
Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is User Flow Diagram popular?
It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.
Related skills
A B Test Design
3.4kOwl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Accessibility Audit
3.4kOwl-Listener/designer-skills
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Accessibility Test Plan
3.4kOwl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Grill Test
3.3krpamis/comet
依次执行原始 grill、to-spec、to-tickets、implement Skill,通过真实会话、审批和实际测试完成代码任务。
Usability Test Plan
3.4kOwl-Listener/designer-skills
Design a usability study — research questions, methodology, participant criteria, metrics, and facilitation guide. Use when planning the study as a whole. For writing the task scenarios inside it, use `test-scenario` (prototyping-testing).
Web Testing
2.2kmrgoonie/claudekit-skills
Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.