customer-empathy — Claude Code skill: what it does, how to install
Question framework to explore user journeys before writing code. Helps eliminate friction and get users to core value without unneeded features.
npx skills add rameerez/claude-code-startup-skills --skill customer-empathy -a claude-codeWhat customer-empathy does
The skill directs the agent to pause before writing code and examine the scenario from the user perspective. It structures the inquiry around several topics: user background, jobs-to-be-done, emotional hurdles, friction reduction, and the shortest route to the aha moment. The focus is specifically on finding an 80/20 balance where users gain maximum value with minimal effort.
This is a prompt exercise. It contains no executable scripts or background integrations. The prompt forces the team to pinpoint details that users ignore, keeping engineering effort away from unnecessary work. Without clear background on real users, the generated responses remain generic.
What it helps with
- map user context and outcomes using jobs-to-be-done
- uncover emotional hurdles and friction in current onboarding flows
- cut secondary features that users skip or ignore
- identify the 80/20 path to an initial aha moment
Example prompts for the agent
- Run the customer-empathy exercise for our onboarding flow
- Review the reporting feature using the customer-empathy questions
- Apply customer-empathy to the user first-login experience
How to install customer-empathy
1Skills CLI (Vercel)
npx skills add rameerez/claude-code-startup-skills --skill customer-empathy -a claude-code2Manually: put the files in place
~/.claude/skills/customer-empathy/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/customer-empathy/
1Skills CLI (Vercel)
npx skills add rameerez/claude-code-startup-skills --skill customer-empathy -a codex2Manually: put the files in place
.agents/skills/customer-empathy/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rameerez/claude-code-startup-skills --skill customer-empathy -a cursor2Manually: put the files in place
.cursor/skills/customer-empathy/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rameerez/claude-code-startup-skills customer-empathy2Manually: put the files in place
.github/skills/customer-empathy/SKILL.md1Skills CLI (Vercel)
npx skills add rameerez/claude-code-startup-skills --skill customer-empathy -a gemini-cli2Platform CLI
gemini skills install https://github.com/rameerez/claude-code-startup-skills --path skills/customer-empathyManually: put the files in place
.devin/skills/customer-empathy/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add rameerez/claude-code-startup-skills --skill customer-empathy -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about customer-empathy
How do I install customer-empathy in Claude Code?
Run npx skills add rameerez/claude-code-startup-skills --skill customer-empathy -a claude-code in your terminal.
What does customer-empathy do?
It runs a focused prompt checklist covering user intentions, emotional friction, and 80/20 value delivery before coding starts.
Does customer-empathy require external tools or API keys?
No, it works as a standalone Markdown prompt file without background scripts or API tokens.
Source text
SKILL.md · MIT
--- name: customer-empathy description: Deep-dive into customer empathy and user journey thinking. Use when designing onboarding, improving UX, planning features, or trying to understand how to delight users faster. --- # Customer Empathy Exercise Pause and deeply empathize with your users before continuing any work. Think through these questions to clarify who you're building for and how to serve them best. ## The Customer **Who is our ideal customer?** - What's their role, context, situation? - What brings them to us right now? **What job are they trying to get done?** - What's the outcome they actually want? - What would "done" look like for them? ## Their Journey **What's their mental state at each step of the way before getting to this point?** - What are they feeling when they first arrive? - What questions are in their head? - Where might they feel confused, frustrated, or stuck? - When do they feel momentum and progress? **What do they care about?** - What matters most to them right now? - What would make them think "yes! This is it!"? **What do they NOT care about?** - What features/details are we obsessing over that they'd skip right past? - What complexity can we remove entirely? ## Delivering Value **How can we best help them?** - What's the single most valuable thing we can do for them? **How do we make them succeed?** - What does success look like from their perspective? - What's blocking them from getting there RIGHT NOW? **How do we make their lives easier?** - What friction can we eliminate? - What can we automate or do for them? ## The Magic **How do we get them to the "aha" moment as fast and easily as humanly possible?** - What IS the "aha" moment? - What's the shortest path to it? - What's currently in the way? **How can we delight them most?** - What would make them smile or say "wow!"? - What unexpected value could we add? **How can we make this as seamless and magical as humanly possible?** - What if this just... worked? - What would "effortless" look like? **How can we make them "wow!" and provide MOST of the value in the SHORTEST time with the LOWEST effort?** - What's our 80/20? - What's the minimum they need to do to get maximum value? --- *Write your answers. Be specific. Challenge assumptions. Think from their shoes, not ours.*
© rameerez · MIT · rameerez/claude-code-startup-skills
