Draft Flow
jeremylongshore/tons-of-skills-marketplace
A skill your agent uses when asked to design a user flow, map how a user moves through a feature, create a wireframe or flow diagram, or document interaction design for a product brief.
Diagram screen-level paths, decision points, and branch logic.
Install User Flow Diagram
$ npx skills add Owl-Listener/designer-skills --skill user-flow-diagram -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills user-flow-diagram --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/prototyping-testing/skills/user-flow-diagram .claude/skills/user-flow-diagram && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "user-flow-diagram" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/prototyping-testing/skills/user-flow-diagram into .claude/skills/user-flow-diagram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-flow-diagram", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/designer-skills/tree/main/prototyping-testing/skills/user-flow-diagramType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/designer-skills --skill user-flow-diagram -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills user-flow-diagram --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/prototyping-testing/skills/user-flow-diagram .agents/skills/user-flow-diagram && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "user-flow-diagram" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/prototyping-testing/skills/user-flow-diagram into .agents/skills/user-flow-diagram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-flow-diagram", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill user-flow-diagram -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills user-flow-diagram --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/prototyping-testing/skills/user-flow-diagram .cursor/skills/user-flow-diagram && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "user-flow-diagram" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/prototyping-testing/skills/user-flow-diagram into .cursor/skills/user-flow-diagram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-flow-diagram", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/designer-skills.git --path prototyping-testing/skills/user-flow-diagram--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/designer-skills --skill user-flow-diagram -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills user-flow-diagram --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/prototyping-testing/skills/user-flow-diagram .gemini/skills/user-flow-diagram && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "user-flow-diagram" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/prototyping-testing/skills/user-flow-diagram into .gemini/skills/user-flow-diagram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-flow-diagram", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/designer-skills user-flow-diagramInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/designer-skills --skill user-flow-diagram -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/prototyping-testing/skills/user-flow-diagram .github/skills/user-flow-diagram && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "user-flow-diagram" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/prototyping-testing/skills/user-flow-diagram into .github/skills/user-flow-diagram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-flow-diagram", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill user-flow-diagram -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/designer-skills user-flow-diagram --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/prototyping-testing/skills/user-flow-diagram .opencode/skills/user-flow-diagram && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "user-flow-diagram" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/prototyping-testing/skills/user-flow-diagram into .opencode/skills/user-flow-diagram/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-flow-diagram", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
user-flow-diagram- GitHub stars
- 2.9k
- Used in
- 1 other repo
- Token cost
- ~448 tokens
- SKILL.md length
- 230 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Diagram screen-level paths, decision points, and branch logic.
- Works in 7 steps: Define the goal the flow accomplishes → Identify the entry point(s) → Map the happy path first → …
- Specifying how a feature is traversed
- SKILL.md covers What You Do, Flow Diagram Elements, Flow Types and Creating Effective Flows, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
User Flow Diagram is an agent skill from Owl-Listener/designer-skills. 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).
Its SKILL.md is about 450 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering UX design, Diagrams and Customer journey mapping. The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.
When your agent uses it
- Specifying how a feature is traversed
- Tasks that involve UX design
- Tasks that involve Diagrams
Example prompts
- “/user-flow-diagram”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Define the goal the flow accomplishes
- Identify the entry point(s)
- Map the happy path first
- Add decision points and branches
- Map error paths and recovery
- Mark exit points
- Note system actions happening in background
What it can do on your machine
Read from SKILL.md and the folder at commit 9a6930c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
User Flow Diagram loads about 448 tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 230 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 230 words, ~448 tokens.
Download SKILL.mdSave it as
.claude/skills/user-flow-diagram/SKILL.md (or your agent's skills folder).- 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
- Define the goal the flow accomplishes
- Identify the entry point(s)
- Map the happy path first
- Add decision points and branches
- Map error paths and recovery
- Mark exit points
- 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, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in prototyping-testing/skills/user-flow-diagram of Owl-Listener/designer-skills.
Open the folder on GitHubat commit 9a6930c
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
User Flow Diagram next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| User Flow Diagram this skillOwl-Listener/designer-skills | 2.9k | 1 repos | ~448 | Automated safety check: Pass | MIT | |
| Draft Flowjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~898 | Automated safety check: Notes | MIT | |
| Archestra Docs Writerarchestra-ai/archestra | 4.4k | — | ~5.3k | Automated safety check: Pass | Custom licence | |
| Bmad UXaj-geddes/claude-code-bmad-skills | 488 | — | ~2k | Automated safety check: Notes | Custom licence | |
| Prototypeplugin87/ux-ui-agent-skills | 1.6k | — | ~614 | Automated safety check: Pass | MIT | |
| Journeyghaida/intent | 207 | — | ~7.6k | Automated safety check: Pass | CC0-1.0 |
Similar skills
Archestra Docs Writer
archestra-ai/archestra
A skill your agent uses when writing, editing, restructuring, or auditing Archestra documentation under docs/pages/ — new feature docs, page rewrites, sidebar and information-architecture changes…
Bmad UX
aj-geddes/claude-code-bmad-skills
Solutioning-phase UX planning skill (optional; activate when the project has a UI).
Prototype
plugin87/ux-ui-agent-skills
Move an idea up the fidelity ladder (content-first → wireframe → low-fi → high-fi → code) with a validation plan at each level, plus user-journey mapping and usability-testing scripts.
Journey
ghaida/intent
Design any user-facing experience end-to-end: task flows, multi-step workflows, navigation structures, onboarding, settings, search, content creation, collaboration, signup, checkout, dashboards…
Product UX Expert
majiayu000/spellbook
Product interaction and UX expert. An agent skill from majiayu000/spellbook.
More from Owl-Listener/designer-skills
All 107 skills in this repoA B Test Design
Owl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size.
Accessibility Test Plan
Owl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.
Aesthetic Usability
Owl-Listener/designer-skills
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.
Affinity Diagram
Owl-Listener/designer-skills
Cluster many qualitative data points into themes and insight statements.
Animation Principles
Owl-Listener/designer-skills
Apply animation principles — easing, staging, follow-through — to one specific UI motion.
Business Design
Owl-Listener/designer-skills
Read financials, map competitive landscapes, and argue design decisions in the language of value.
Related
Categories
Questions about User Flow Diagram
What does User Flow Diagram do?
Diagram screen-level paths, decision points, and branch logic. User Flow Diagram is an agent skill from Owl-Listener/designer-skills. Diagram screen-level paths, decision points, and branch logic.
When should I use User Flow Diagram?
User Flow Diagram fits situations like: specifying how a feature is traversed; tasks that involve UX design; tasks that involve Diagrams.
How do I install User Flow Diagram in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill user-flow-diagram -a claude-code`. Or copy the skill folder (prototyping-testing/skills/user-flow-diagram in Owl-Listener/designer-skills) into .claude/skills/user-flow-diagram in your project. Claude Code loads it when a task matches its description.
How do I install User Flow Diagram in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill user-flow-diagram -a codex`. Or copy the skill folder (prototyping-testing/skills/user-flow-diagram in Owl-Listener/designer-skills) into .agents/skills/user-flow-diagram in your project. Codex loads it when a task matches its description.
Can I use User Flow Diagram in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designer-skills --skill user-flow-diagram -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/user-flow-diagram, .gemini/skills/user-flow-diagram, .github/skills/user-flow-diagram and .opencode/skills/user-flow-diagram in your project.
What does User Flow Diagram need to run?
SKILL.md names no scripts, command-line tools or credentials: User Flow Diagram is instructions for the agent only.
Does User Flow Diagram access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is User Flow Diagram safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does User Flow Diagram use?
User Flow Diagram is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does User Flow Diagram use?
About 448 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to User Flow Diagram?
Skills that share tags, products or a category with User Flow Diagram: Draft Flow (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Archestra Docs Writer (archestra-ai/archestra, 4.4k stars), Bmad UX (aj-geddes/claude-code-bmad-skills, 488 stars) and Prototype (plugin87/ux-ui-agent-skills, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains User Flow Diagram?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,871 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.
Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.