Affinity Diagram

Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.

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 affinity-diagram
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/affinity-diagram ~/.claude/skills/affinity-diagram

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

From the SKILL.md

# Affinity Diagram

Organize qualitative research data into themed clusters and insight statements.

## Context

You are a UX researcher synthesizing qualitative data for $ARGUMENTS. If the user provides files (interview notes, observation data, survey responses), read them first.

## Instructions

1. **Extract data points**: Pull individual observations, quotes, and notes from the raw data.
2. **Bottom-up clustering**: Group related data points into natural clusters (do not start with predefined categories).
3. **Name each cluster**: Create descriptive theme labels that capture the essence of each group.
4. **Create hierarchy**: Organize clusters into higher-level themes (typically 3-5 top-level themes).
5. **Write insight statements**: For each theme, write a clear insight statement that captures the "so what?"
6. **Identify patterns**: Note frequency, intensity, and connections between themes.
7. **Prioritize**: Rank insights by impact on design decisions.
8. Present the affinity diagram as a structured hierarchy with insight statements and supporting evidence.

## Cross-Interview Sampling Principle

**Index evenly across all participants.** When working from multiple interview transcripts, process each one fully before clustering. Do not over-represent early transcripts or the most recent input.

- Treat each participant as an equal source of signal
- Tag every observation with its participant ID (P1, P2, P3...) before grouping
Read the full skill on GitHub

Details

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

FAQ

What does the Affinity Diagram skill do?

Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.

How do I install the Affinity Diagram 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 Affinity Diagram 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

Animation Principles

3.4k

Owl-Listener/designer-skills

Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.

Frontend & Design447

Card Sort Analysis

3.4k

Owl-Listener/designer-skills

Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).

Frontend & Design447

Verify

2.1k

ai4s-research/open-science

Verify apps/desktop frontend changes visually without launching the Tauri app or a live model

Frontend & Design231

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