customer-journey-map
Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey.
- License 许可
- MIT
- 最近更新
- 2026-11-05
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- customer-journey-map
- description
- Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey.
03 SKILL.md 正文
Customer Journey Map
Map the end-to-end customer experience from awareness through advocacy, identifying emotions, pain points, and improvement opportunities at each stage.
Context
You are creating a customer journey map for $ARGUMENTS.
If the user provides files (interview transcripts, survey data, analytics, support tickets, or existing journey maps), read them first. Use web search to understand the product if a URL is provided.
Instructions
-
Define the persona: Who is traveling this journey? Use a specific persona with JTBD, not a generic user.
-
Map the journey stages (adapt to the product):
Stage Description Awareness How do they first learn about the product? Consideration What do they evaluate? What alternatives do they compare? Acquisition How do they sign up or purchase? Onboarding First experience with the product — time to value Engagement Regular usage — building habits Retention What keeps them coming back? What might cause churn? Advocacy When and why do they recommend the product to others? -
For each stage, document:
- Touchpoints: Where the user interacts with the product, brand, or team (website, email, in-app, support, social media)
- User actions: What they do at this stage
- Thoughts & questions: What's on their mind ("Is this worth my time?" "How do I...?")
- Emotions: How they feel (excited, confused, frustrated, delighted) — rate on a scale or use emoji indicators
- Pain points: Friction, confusion, drop-off risks
- Opportunities: How to improve the experience at this point
-
Identify critical moments:
- Aha moment: When the user first experiences core value
- Moments of truth: Decision points where they commit or abandon
- Churn triggers: Where users most commonly drop off
-
Create the journey map table:
Stage Touchpoint User Action Emotion Pain Point Opportunity -
Recommend prioritized improvements:
- Which pain points have the highest impact on conversion or retention?
- What quick wins can improve the experience immediately?
- What requires deeper investment but has the biggest payoff?
Think step by step. Save as a markdown document. For visual journey maps, suggest the user create one in Miro or FigJam using this analysis as the foundation.
Further Reading
04 同仓库更多 Skills
taste-design
Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.
stitch-loop
Teaches agents to iteratively build websites using Stitch with an autonomous baton-passing loop pattern
site-md
Analyze a project description or site requirements and synthesize a project constitution into SITE.md for the Stitch Build Loop
enhance-prompt
Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
design-md
Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files
stitch::upload-to-stitch
Upload local assets (images, mockups, extracted HTML, design markdown) to a Stitch project. ALWAYS use this skill when you need to upload visual assets, HTML pages, or design docs to Stitch, particularly when direct MCP tool calls fail or truncate due to base64 token limits.