Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points. Use when improving an existing experience. For the multi-channel ecosystem use `experience-map` (ux-strategy); for screen-level paths use `user-flow-diagram` (prototyping-testing).
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:
Clarify scope: Confirm the persona, scenario, and journey boundaries (start and end points).
Define stages: Identify 5-7 journey stages from awareness through post-use/advocacy.
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
Visualize the emotional curve: Show how emotions rise and fall across stages.
Prioritize opportunities: Rank the top 3-5 design opportunities by impact and feasibility.
Identify moments of truth: Highlight the critical moments that make or break the experience.
Think step by step. Present in a clear, structured format.
Further Reading
Mapping Experiences — Jim Kalbach
The Elements of User Experience — Jesse James Garrett
presentation-deckowl-listenerStructure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use `case-study`; for the written argument use `design-rationale`.2,8002,800 installs on skills.sh0
typography-scaleowl-listenerCreate a modular type scale with size, weight, and line-height relationships. Use when establishing typographic structure. For line length only use `readable-measure`; for judging type on an existing screen use `critique-typography` (visual-critique).2,3002,300 installs on skills.sh0
visual-hierarchyowl-listenerEstablish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order. Use when composing new work. For judging an existing screen, use `critique-visual-hierarchy` (visual-critique).2,3002,300 installs on skills.sh0
color-systemowl-listenerBuild a product colour system — tonal scales, semantic roles, and contrast compliance. Use when defining or rebuilding colour from scratch. For dark-mode adaptation use `dark-mode-design`; for chart palettes use `data-visualization`; for multi-brand token architecture use `theming-system` (design-systems).2,2002,200 installs on skills.sh0
dark-mode-designowl-listenerAdapt an existing palette to dark mode — surface elevation, contrast rebalancing, and desaturation rules. Use when you already have a light palette to translate. For building the base palette first, use `color-system`.2,2002,200 installs on skills.sh0
