journey-map
Skill19 starsChanged 6 days agoMITView on GitHub
Map the key user journeys for a prototype, including happy paths, edge cases, decision points, and recovery flows.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- miguelclavel/ux-research-skillstheir own version, first seen Nov 8, 2026
- lalulali/vespyrtheir own version, first seen Nov 6, 2026
- coco-research/cocotheir own version, first seen Nov 1, 2026
- Pearl1531/Archetype-talktheir own version, first seen Oct 13, 2026
- Mozurok/fhorja.devtheir own version, first seen Oct 8, 2026
- cabbagecachekid/neon-jetpacktheir own version, first seen Aug 19, 2026
Used with
Projects with it also use interview-guide and prioritize.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
nbirknerSkillinterview-guide
Use when preparing to conduct user research interviews and needing structured JTBD-based questions. Also use when starting a new discovery research effort or when existing interview questions feel generic. Keywords: interview guide, user research questions, discovery interview, JTBD questions, research script.
Also in 4 projects that use this
blueOctopusAISkillprioritize
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- coco-research/coco★ 797same name
- launchapp-dev/animus-cli★ 39same name
- lalulali/vespyr★ 11same name
- Mozurok/fhorja.dev★ 10same name
- Pearl1531/Archetype-talk★ 2same name
- miguelclavel/ux-research-skills★ 1same name
- miovrag/claude-skills★ 1same name
- cabbagecachekid/neon-jetpack★ 0same name
- nbirkner/digital-brain★ 0same name
- talgacapri/pm-os★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository67 other files it gives its agents.
- accessibility-precheckSkill
- cognitive-friction-detectorSkill
- cognitive-walkthrough-beadsSkill
- cognitive-walkthroughSkill
- conceptual-model-beadsSkill
- conceptual-modelSkill
- consistency-audit-beadsSkill
- consistency-auditSkill
- error-and-time-metrics-analyzerSkill
- failure-path-audit-beadsSkill
- failure-path-auditSkill
- field-study-plannerSkill
- heuristic-eval-beadsSkill
- heuristic-evalSkill
- high-fidelity-prototype-plannerSkill
- information-architecture-beadsSkill
- information-architectureSkill
- interaction-type-selectorSkill
- journey-map-beadsSkill
- journey-mapSkill
- low-fidelity-prototype-plannerSkill
- mental-model-checkerSkill
- persona-synthesizerSkill
- prototype-hci-pack-beadsSkill
- prototype-hci-packSkill
- representative-task-writerSkill
- satisfaction-questionnaire-writerSkill
- state-model-beadsSkill
- state-modelSkill
- task-analysis-writerSkill
- usability-test-plannerSkill
- vocabulary-audit-beadsSkill
- vocabulary-auditSkill
- wireframe-criticSkill
- accessibility-precheckSkill
- cognitive-friction-detectorSkill
- cognitive-walkthrough-beadsSkill
- cognitive-walkthroughSkill
- conceptual-model-beadsSkill
- conceptual-modelSkill
- consistency-audit-beadsSkill
- consistency-auditSkill
- error-and-time-metrics-analyzerSkill
- failure-path-audit-beadsSkill
- failure-path-auditSkill
- field-study-plannerSkill
- heuristic-eval-beadsSkill
- heuristic-evalSkill
- high-fidelity-prototype-plannerSkill
- information-architecture-beadsSkill
- information-architectureSkill
- interaction-type-selectorSkill
- journey-map-beadsSkill
- low-fidelity-prototype-plannerSkill
- mental-model-checkerSkill
- persona-synthesizerSkill
- prototype-hci-pack-beadsSkill
- prototype-hci-packSkill
- representative-task-writerSkill
- satisfaction-questionnaire-writerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use ultrathink. Work from the current prototype, routes, components, docs, screenshots, and any existing flows.
- Very specific: line 14
Write docs/hci/user-journeys.md unless the user asked for another path.
- Distinctive: line 15
Create the directory if it does not exist.
- Distinctive: line 29
Add Mermaid flowcharts for the most important journeys.
- Distinctive: line 52
Keep the flow specific to the actual prototype.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Map the key user journeys for this scope:
$ARGUMENTS
Use ultrathink. Work from the current prototype, routes, components, docs, screenshots, and any existing flows. Infer missing pieces conservatively.
Output
Write docs/hci/user-journeys.md unless the user asked for another path.
Create the directory if it does not exist.
Required process
- Identify the 3 to 7 most important journeys.
- Prioritize first-time use, core task completion, edit/undo, failure recovery, and returning user behavior.
- For each journey, document:
- goal
- trigger / entry point
- steps
- decision points
- alternate branches
- errors and recovery
- exit state
- likely confusion points
- Add Mermaid flowcharts for the most important journeys.
- Summarize cross-journey friction themes.
Output structure
For each journey use:
- Journey name
- User goal
- Preconditions
- Main flow
- Alternative flow(s)
- Error path(s)
- Exit state
- Confusion risks
- Design recommendation(s)
Synthesis
End with:
- journeys most likely to fail for first-time users
- shared friction points across multiple journeys
- dead ends and missing recovery paths
- design changes with the highest impact on task completion
Quality bar
- Keep the flow specific to the actual prototype.
- Focus on what the user must perceive and decide, not just backend events.
- Flag hidden dependencies, missing feedback, dead ends, and branch explosions.
Deliverable style
- Clear headings
- Markdown tables
- Mermaid diagrams where useful
- Direct language
- No filler
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

