360 Secure SkillHub
360 安全技能中心

user-flow-diagram

用于按用户目标绘制屏幕级用户流程图,指导识别入口、主路径、决策分支、错误恢复、系统动作和退出点,并说明流程类型、图元与标注规范。该 Skill 只提供方法,不包含绘图工具或文件导出功能。

Owl-Listener
热度 30.52
最近更新 2026-10-19 04:18:31
分类:创作依赖:纯提示词应用场景:UI 原型 / 工作流

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add owl-listener/designer-skills/user-flow-diagram
Metadata
name
user-flow-diagram
description
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).

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