dotfiles/dot_config/skillshare/skills/customer-journey-map/SKILL.md
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.
npx skillsauth add pkking/dotfiles customer-journey-mapInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Map the end-to-end customer experience from awareness through advocacy, identifying emotions, pain points, and improvement opportunities at each stage.
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.
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:
Identify critical moments:
Create the journey map table:
| Stage | Touchpoint | User Action | Emotion | Pain Point | Opportunity | |---|---|---|---|---|---|
Recommend prioritized improvements:
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.
testing
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
tools
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
tools
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
data-ai
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.