owl-listener/designer-skills

user-flow-diagram

Diagram screen-level paths, decision points, and branch logic.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/owl-listener/designer-skills --skill user-flow-diagram

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

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

Verwandte Aufgaben

aus demselben Repository

Weitere Skills

Alle Skills