Journey Map
- 950 installs
- 1.9k repo stars
- Updated June 14, 2026
- owl-listener/designer-skills
Journey Map is a UX research skill that generates end-to-end user journey maps with stages, touchpoints, emotions, pain points, and opportunity areas for developers and designers who must understand experience friction b
About
Journey Map is an installable skill from owl-listener/designer-skills that creates comprehensive user journey maps for product design and UX analysis. It follows journey-mapping practice from Jim Kalbach's Mapping Experiences, structuring stages, touchpoints, channels, emotions, and pain points across the full experience. The skill reads supplied research data, personas, or analytics when provided. Developers and design teams reach for Journey Map when mapping a product, feature, or service flow to surface friction and improvement opportunities before UI implementation. Output is visual and analytical, aimed at design critique and prioritization.
- Creates end-to-end journey maps with 5-7 stages from awareness to advocacy
- Captures user goals, actions, touchpoints, thoughts, emotions, pain points, and opportunities per stage
- Produces both current-state (as-is) and future-state opportunity areas
- Persona-specific mapping when user data or files are provided
- Follows Jim Kalbach Mapping Experiences methodology
Journey Map by the numbers
- 950 all-time installs (skills.sh)
- +44 installs in the week ending Jul 29, 2026 (Skillselion tracking)
- Ranked #434 of 1,888 Design & UI/UX skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/designer-skills --skill journey-mapAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 950 |
|---|---|
| repo stars | ★ 1.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | June 14, 2026 |
| Repository | owl-listener/designer-skills ↗ |
How do you map end-to-end user journey friction?
Generate a complete visual and analytical user journey map that reveals friction, emotions, and improvement opportunities before committing to features.
Who is it for?
Developers and designers preparing feature work who need a structured journey map from personas, research files, or stated product flows.
Skip if: Teams that already finalized UI specs and only need pixel-perfect component implementation without experience mapping.
When should I use this skill?
A developer or designer asks to map the full user experience, touchpoints, emotions, or pain points for a product or feature.
What you get
User journey map with stages, touchpoints, channel notes, emotion curves, pain points, and prioritized opportunity areas.
- user journey map document
- pain point and opportunity inventory
Files
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 Garrett
Related skills
Frontend DesignGenerate distinctive, production-grade frontend interfaces and components that avoid generic AI aesthetics.698k164k
Web Design GuidelinesAutomatically audit frontend code against the latest Vercel Web Interface Guidelines for consistency, accessibility, and UX quality.486k29.4k
Lark WhiteboardGenerate valid Lark Whiteboard (Feishu Board) documents with correctly placed connectors, automatic routing, and proper schema compliance directly from agent inst382k15.8k
Sleek Design Mobile AppsGenerate mobile app screens and UI from plain English descriptions using the Sleek.design API.315k470
Design Taste FrontendOverride generic LLM frontend output with intentional, metric-driven UI/UX taste.284k66.9k
Ui Ux Pro MaxGet instant, high-quality UI/UX decisions, component recommendations, style guidance, and code improvements across web and mobile projects.282k109kHow it compares
Choose Journey Map for holistic experience visualization across stages; use usability test-scenario skills when you already need executable participant tasks.
FAQ
What does Journey Map include in output?
Journey Map produces stages, touchpoints, channels, emotions, pain points, and opportunity areas for a product, feature, or service. It can ingest research data, personas, or analytics when the user provides files.
When should developers use Journey Map?
Journey Map fits pre-build UX analysis when teams need to visualize end-to-end experience friction. The skill description targets mapping before committing to feature implementation.
Is Journey Map safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.