Empathy Map

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`.

3,414 stars 447 forksFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Owl-Listener/designer-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Owl-Listener/designer-skills --skill empathy-map
Manual install
git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/design-research/skills/empathy-map ~/.claude/skills/empathy-map

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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?
Read the full skill on GitHub

Details

Skill name
empathy-map
Path
design-research/skills/empathy-map/SKILL.md
License
MIT
Repo updated
5 September 2026

FAQ

What does the Empathy Map skill do?

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`.

How do I install the Empathy Map skill?

Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Empathy Map popular?

It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.

Related skills

A B Test Design

3.4k

Owl-Listener/designer-skills

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

Testing & QA447

Accessibility Audit

3.4k

Owl-Listener/designer-skills

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

Frontend & Design447

Accessibility Test Plan

3.4k

Owl-Listener/designer-skills

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

Testing & QA447

Error Handling UX

3.4k

Owl-Listener/designer-skills

Design error prevention, detection, and recovery across a product — message content, placement, and escape routes. Use when errors span multiple flows. For validation inside a single form, use `form-design`.

Frontend & Design447

Design Token

3.4k

Owl-Listener/designer-skills

Define and organise tokens for colour, spacing, type, and elevation with naming and usage rules. Use when establishing the token layer. For auditing existing usage use `design-token-audit` (designer-toolkit); for multi-brand mapping use `theming-system`.

Frontend & Design447

Feedback Patterns

3.4k

Owl-Listener/designer-skills

Design confirmations, status updates, and notifications that tell users an action registered. Use when the system must acknowledge success or change. For waiting states use `loading-states`; for failures use `error-handling-ux`.

Frontend & Design447

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.