journey-map
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).
- Installs
- 2.2K
- Last 24h
- +23
- Trending rank
- #5240
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/designer-skills --skill journey-map- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads journey-map automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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:
- 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
FAQ
What does the journey-map skill do?
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).
How do I install journey-map?
Run npx skills add https://github.com/owl-listener/designer-skills --skill journey-map in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/journey-map/ (personal) or .claude/skills/journey-map/ (project).
Which AI agents can use journey-map?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is journey-map safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains journey-map?
It is published by owl-listener in owl-listener/designer-skills. It has 2,161 recorded installs.
More from owl-listener/designer-skills
presentation-deck
owl-listener/designer-skills
Structure 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.
typography-scale
owl-listener/designer-skills
Create 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).
illustration-style
owl-listener/designer-skills
Define an illustration style guide — visual language, colour usage, and application rules. Use when commissioning or standardising illustration. For icons, use icon-system (design-systems).
visual-hierarchy
owl-listener/designer-skills
Establish 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).
color-system
owl-listener/designer-skills
Build 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).
dark-mode-design
owl-listener/designer-skills
Adapt 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.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.