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 從公開儲存庫中收錄這些內容。

檢舉或申請下架