User Flow Diagram

owl-listener/designer-skills/prototyping-testing/skills/user-flow-diagram

作者 owl-listener9a6930cf84a8无许可证2.8K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库4周前更新

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).

仅含说明Design & Creative
AI 生成的概览

指导创建用户流程图,映射页面路径、决策点、分支与错误路径。

功能
该技能提供创建用户流程图的指导,展示用户如何在产品中移动以达成目标。它定义了入口点、页面、决策、操作、系统流程、终点和连接线等图示元素,并涵盖任务流、用户流和线框流。它还给出分步创建顺序以及标注和最佳实践建议。
适用场景
适用于在页面层面说明某个功能的遍历方式,包括决策点和分支逻辑。适合为单一用户目标梳理正常路径、错误路径和恢复步骤。
运行要求
无需脚本或工具,仅为说明性技能。只需一个智能体来应用这些指导。

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

来源与署名

来源:owl-listener/designer-skills位于prototyping-testing/skills/user-flow-diagram提交9a6930c

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架