Skip to main content
affpapa.org
RU EN
skill CX Codex

empathy-map — Claude Code skill: a Says, Thinks, Does, Feels map

Builds an empathy map for one user or segment across four quadrants, so the team shares the same picture of the user.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add Owl-Listener/designer-skills --skill empathy-map -a claude-code
Open on GitHub

What empathy-map does

The skill walks the agent through a UX researcher's steps: confirm who the map is for, then sort the material into quadrants. Says holds direct quotes from interviews, Thinks covers beliefs and worries inferred from behaviour, Does captures observed actions and workarounds, Feels collects emotional states and motivations. From there the agent names goals, pain points and design implications, and closes by listing what is still unknown.

Hand it files — interview transcripts, observation notes, survey exports — and it reads them first. The map is meant to come from real research data rather than assumptions, so without source files the quadrants stay thin and the agent works only from your description. Worth gathering the material before you run it.

It is not a replacement for user-persona, which builds a composite archetype with goals and behaviours. For themes that repeat across sessions, use affinity-diagram. MIT licensed, installed with one npx skills add command.

What it helps with

  • sort interview transcripts into Says, Thinks, Does, Feels
  • show the team where what users say diverges from what they do
  • pull barriers and frustrations out of observation notes
  • turn raw research data into design implications
  • flag research gaps before the next round of interviews

Example prompts for the agent

  • Build an empathy map for new users from these interview transcripts
  • Create an empathy map for the small business owner segment, files are in research/
  • Map Says, Thinks, Does, Feels from my observation notes and list the gaps

How to install empathy-map

1Skills CLI (Vercel)

npx skills add Owl-Listener/designer-skills --skill empathy-map -a claude-code

2Manually: put the files in place

~/.claude/skills/empathy-map/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/empathy-map/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about empathy-map

How do I install empathy-map in Claude?

Run npx skills add Owl-Listener/designer-skills --skill empathy-map -a claude-code. The skill lands at ~/.claude/skills/empathy-map/SKILL.md.

What does empathy-map do?

It builds an empathy map for one user or segment: quotes, beliefs, actions and emotions, plus goals and pain points. It finishes with design implications and open questions.

How is empathy-map different from user-persona?

An empathy map covers one user or segment across four quadrants. For a composite archetype with goals and behaviours use user-persona; for themes that repeat across sessions use affinity-diagram.

Source text

SKILL.md · MIT 
---
name: empathy-map
description: Build a Says, Thinks, Does, Feels map for one user or segment. Use when sharing user understanding quickly. For a composite archetype with goals and behaviours use `user-persona`; for cross-session themes use `affinity-diagram`.
---

# Empathy Map

Build an empathy map to synthesize user research and align the team around user understanding.

## Context

You are a senior UX researcher helping a design team build an empathy map for $ARGUMENTS. If the user provides files (interview transcripts, observation notes, survey data), read them first.

## Domain Context

- Empathy Maps (Dave Gray, XPLANE): A collaborative tool to externalize what we know about a user type.
- Four quadrants: Says (direct quotes), Thinks (inferred beliefs), Does (observed actions), Feels (emotional states).
- Also capture Goals (what they want to achieve) and Pain Points (barriers and frustrations).
- Best created from actual research data, not assumptions.

## Instructions

The user will describe their user type and available research data. Work through these steps:

1. **Clarify the user**: Confirm who this empathy map is for (persona, segment, or user type).
2. **Map each quadrant**:
  - **Says**: Direct quotes and statements from research (use actual quotes where available)
  - **Thinks**: Beliefs, concerns, and thoughts inferred from behavior and context
  - **Does**: Observable actions, behaviors, and workarounds
  - **Feels**: Emotional states, anxieties, and motivations
3. **Identify goals**: What is this user trying to achieve?
4. **Identify pain points**: What barriers, frustrations, or unmet needs exist?
5. **Extract insights**: What design implications emerge from this empathy map?
6. **Note gaps**: What do we still need to learn?
7. Think step by step. Present the empathy map in a clear, visual-friendly format.

## Further Reading

- Gamestorming — Dave Gray
- Lean UX — Jeff Gothelf and Josh Seiden

© Owl-Listener · MIT · Owl-Listener/designer-skills

Similar skills

Everything for Design →
customer-journey-map phuryn Builds an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Useful for experience research and onboarding work. CX Codex +1 3,100installs ux-researcher VoltAgent Community This subagent plans UX research, interprets user behavior, and turns findings into design recommendations. Use it to validate a design decision or investigate user needs. 703installs ux-principles manutej Gives your coding agent usability heuristics, user research methods and accessibility checks, so interface work follows known rules instead of guesswork. CX Codex +1 836installs ux-research-discovery-testing hueyexe Gives your agent a working method for discovery interviews, usability tests and synthesis, so product calls rest on observed behavior instead of opinions. CX Codex +1 468installs investigate ghaida Runs user research from planning to synthesis: interview guides, surveys, usability tests, diary studies, and finding analysis. CX Codex +1 2,700installs om-synthetic-users open-mercato Constructs synthetic persona panels from repository materials to test product flows and surface objections under decision pressure. CX Codex +1 1,600installs

From the same set111

pattern-library This skill turns recurring UX solutions into pattern entries with problem context, behavior, examples, accessibility notes, and related patterns. CX Codex +1 2,100installs affinity-diagram This skill groups observations and quotes from interviews into themed clusters and writes insight statements. Useful when you have many sources to synthesise. CX Codex +1 2,100installs documentation-template Generates reusable documentation scaffolds for design system components, patterns, and foundations. Use it when setting a shared documentation standard across your team. CX Codex +1 2,100installs naming-convention Sets one naming scheme for components, tokens and layers so names stop drifting between files. CX Codex +1 2,100installs handoff-spec Generates developer handoff specifications covering measurements, interaction states, responsive breakpoints, and edge cases before engineering starts. CX Codex +1 2,100installs experience-map The skill maps every touchpoint, channel and relationship across a service. Useful when the experience spans more than one product. CX Codex +1 2,100installs jobs-to-be-done A Claude Code skill that runs a Jobs-to-Be-Done pass: splits a task into functional, emotional and social parts, then returns a map with design implications. CX Codex +1 2,100installs user-persona This skill builds 2-4 research-grounded personas from interview transcripts, surveys, or analytics. It helps teams align design decisions with observed user behavior. CX Codex +1 2,100installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor