mcpField
U
user-flow-diagram

user-flow-diagram

github.com/owl-listenerDesign & UI3.1k2.4k installsUpdated 8w ago
Repository

About user-flow-diagram

A design skill for mapping how users move through a product to reach a goal. It covers task, user, and wire flows, including decision branches, system actions, and error recovery.

Key features

  1. 01Task, user, and wire flow diagrams
  2. 02Entry, screen, action, and decision notation
  3. 03Mapping branches and error recovery
  4. 04Annotations for system events and delays
  5. 05Guidance for readable, consistent flows

Use cases

  1. 01Map the steps for completing a product task
  2. 02Show alternate paths based on user choices
  3. 03Document errors and recovery routes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owl-listener/designer-skills --skill user-flow-diagram

After installing, type/user-flow-diagramin Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported