user-journey-mapping — Claude Code skill: maps and setup
The user-journey-mapping Claude Code skill lays out user journeys with stages, touchpoints, emotions, and friction points. It activates for experience mapping or conversion-flow analysis.
MIT 102 installs ★ 71 updated 2026-06-29
npx skills add NickCrew/Claude-Cortex --skill user-journey-mapping -a claude-codeWhat user-journey-mapping does
The skill breaks a user experience into stages and records what people do, where they interact, how they feel, and where problems arise. It includes a journey-map template, an e-commerce checkout example, and a research-methods reference at skills/user-journey-mapping/references/research-methods.md.
A matrix of impact and frequency helps rank pain points. The guide also suggests comparing metrics before and after a design change. Maps should reflect findings from real user research rather than an assumed ideal flow.
What it helps with
- Break a user experience into stages and touchpoints
- Locate drop-off points in a conversion funnel
- Track emotional shifts and friction during key interactions
- Connect user pain points with improvement ideas
Example prompts for the agent
- Map the checkout journey and mark the stages where customers run into problems.
- Trace the customer experience from first discovering the product to using it.
- Find drop-off points in this conversion flow and suggest metrics to track.
How to install user-journey-mapping
1Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill user-journey-mapping -a claude-code2Manually: put the files in place
~/.claude/skills/user-journey-mapping/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/user-journey-mapping/
1Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill user-journey-mapping -a codex2Manually: put the files in place
.agents/skills/user-journey-mapping/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill user-journey-mapping -a cursor2Manually: put the files in place
.cursor/skills/user-journey-mapping/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install NickCrew/Claude-Cortex skills/user-journey-mapping2Manually: put the files in place
.github/skills/user-journey-mapping/SKILL.md1Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill user-journey-mapping -a gemini-cli2Platform CLI
gemini skills install https://github.com/NickCrew/Claude-Cortex --path skills/user-journey-mappingManually: put the files in place
.devin/skills/user-journey-mapping/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill user-journey-mapping -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about user-journey-mapping
How do I install user-journey-mapping in Claude Code?
Run npx skills add NickCrew/Claude-Cortex --skill user-journey-mapping -a claude-code. The skill file is located at ~/.claude/skills/user-journey-mapping/SKILL.md.
What does user-journey-mapping do?
It helps map a user experience by stage, covering actions, touchpoints, and emotions. The map also records friction points and opportunities for improvement.
What does a user journey map include?
The template covers stages, user goals and actions, touchpoints, emotions, pain points, opportunities, and metrics. It also describes an impact-and-frequency matrix for ranking issues.
Source text
SKILL.md · MIT
--- name: user-journey-mapping description: Create comprehensive user journey maps that identify pain points, opportunities, and emotional states across touchpoints. Use when mapping user experiences or analyzing conversion flows. keywords: - user journey - journey map - customer experience - touchpoints - conversion funnel triggers: - journey map - user journey - customer journey - experience map - conversion flow --- # User Journey Mapping Comprehensive guide to creating user journey maps that reveal pain points, opportunities, and emotional states across the entire user experience. ## When to Use This Skill - Mapping end-to-end user experiences - Identifying conversion funnel drop-off points - Understanding emotional states during key interactions - Discovering optimization opportunities - Aligning teams around user perspective ## Quick Reference | Task | Load reference | | --- | --- | | **Research Methods** | `skills/user-journey-mapping/references/research-methods.md` | ## Journey Map Components ### 1. Stages Define the major phases users go through: ``` Awareness → Consideration → Decision → Onboarding → Usage → Advocacy ``` ### 2. User Actions What the user does at each stage: - Searches, browses, compares - Signs up, configures, learns - Uses features, seeks help - Shares, recommends, upgrades ### 3. Touchpoints Where interaction happens: - Website, mobile app, email - Support chat, documentation - Social media, reviews - In-person, phone ### 4. Emotions How users feel (use emoticons or scale): ``` 😊 Delighted → 😐 Neutral → 😤 Frustrated → 😡 Angry ``` ### 5. Pain Points Where friction occurs: - Confusion, delays, errors - Missing information - Poor feedback - Technical issues ### 6. Opportunities Where we can improve: - Quick wins - Major improvements - Innovation opportunities ## Journey Map Template ```markdown ## User Journey: [Persona Name] - [Goal] ### Stage 1: [Stage Name] **User Goal**: [What they're trying to achieve] **Actions**: - [Action 1] - [Action 2] **Touchpoints**: [Where interaction happens] **Emotions**: [😊/😐/😤/😡] - [Why they feel this way] **Pain Points**: - [Pain point with impact] **Opportunities**: - [Opportunity with potential impact] **Metrics**: [How we measure this stage] --- [Repeat for each stage] ``` ## Example Journey Map ### E-commerce Checkout Journey | Stage | Awareness | Cart | Checkout | Payment | Confirmation | |-------|-----------|------|----------|---------|--------------| | **Actions** | Browse, compare | Add items, review | Enter details | Pay | Receive | | **Emotions** | 😊 Excited | 😐 Considering | 😤 Tedious | 😰 Anxious | 😊 Relieved | | **Pain Points** | Too many options | Price unclear | Too many fields | Security fears | No ETA | | **Opportunities** | Recommendations | Clear pricing | Autofill | Trust signals | Tracking | ## Best Practices ### Do's - Base on real user research, not assumptions - Include both digital and non-digital touchpoints - Map emotional highs and lows - Quantify with metrics where possible - Involve cross-functional stakeholders ### Don'ts - Don't map the ideal journey - map reality - Don't focus only on your touchpoints - Don't ignore competitor alternatives - Don't skip the "boring" stages - Don't create and forget - iterate ## Integration with Design 1. **Identify critical moments**: Where do emotions shift? 2. **Prioritize pain points**: Impact × Frequency matrix 3. **Design interventions**: Targeted improvements 4. **Measure success**: Before/after metrics 5. **Iterate**: Journey maps are living documents ## Resources - [Nielsen Norman Group Journey Mapping Guide](https://www.nngroup.com/articles/journey-mapping-101/) - [Service Design Tools](https://servicedesigntools.org/tools/customer-journey-map)
© NickCrew · MIT · NickCrew/Claude-Cortex