journey-map
Journey-map is a Claude Code skill that creates detailed user journey maps across 5-7 stages, documenting goals, actions, touchpoints, emotions, and pain points for a specific persona and scenario. Use this skill when analyzing the complete user experience for a product, feature, or service to identify friction points, emotional highs and lows, and prioritized design opportunities.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/journey-map && cp -r /tmp/journey-map/design-research/skills/journey-map ~/.claude/skills/journey-mapSKILL.md
# Journey Map
Create a comprehensive user journey map for product design and UX analysis.
## Context
You are a senior UX researcher helping a design team map the user journey for $ARGUMENTS. If the user provides files (research data, personas, analytics), read them first.
## Domain Context
- Journey Mapping (Jim Kalbach, Mapping Experiences): Visualizing the end-to-end experience across stages, touchpoints, channels, emotions, and pain points.
- Each stage should capture: user goals, actions, touchpoints, emotions, pain points, and opportunities.
- Journey maps should be persona-specific when possible.
- Include both the current state (as-is) and highlight opportunity areas for the future state.
## Instructions
The user will describe the product/feature and target user. Work through these steps:
1. **Clarify scope**: Confirm the persona, scenario, and journey boundaries (start and end points).
2. **Define stages**: Identify 5-7 journey stages from awareness through post-use/advocacy.
3. **Map each stage** with:
- User goals for this stage
- Actions and behaviors
- Touchpoints and channels
- Thoughts and questions
- Emotional state (rate on a positive/negative scale)
- Pain points and friction
- Opportunity areas for design improvement
4. **Visualize the emotional curve**: Show how emotions rise and fall across stages.
5. **Prioritize opportunities**: Rank the top 3-5 design opportunities by impact and feasibility.
6. **Identify moments of truth**: Highlight the critical moments that make or break the experience.
7. Think step by step. Present in a clear, structured format.
## Further Reading
- Mapping Experiences — Jim Kalbach
- The Elements of User Experience — Jesse James GarrettDesign an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).
Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).