user-flow-diagram
User-flow-diagram creates flowcharts mapping how users navigate through product interfaces to complete goals, including decision points, alternative paths, and error handling. Use this skill when documenting user journeys, designing new features, communicating product logic to stakeholders, or identifying gaps in existing user experiences.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/user-flow-diagram && cp -r /tmp/user-flow-diagram/prototyping-testing/skills/user-flow-diagram ~/.claude/skills/user-flow-diagramSKILL.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) - Use consistent notation - Label every arrow with the trigger/action
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`.
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).
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).
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).
Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).