Affinity diagram
Skill Infrasity-Labs/dev-gtm-claude-skills/.claude/skills/affinity-diagram
Open-source Claude skills for GEO, AI discoverability, and developer GTM workflows. Built for developer-focused companies that want their documentation to be found, parsed, and cited by AI systems.
npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill affinity-diagramAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Organize qualitative research data into an affinity diagram with themes, clusters, and insight statements. Use when synthesizing large amounts of qualitative data from interviews, observations, or surveys.
SKILL.md
2.0 KB, as published. Nobody here has run it
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
- Extract data points: Pull individual observations, quotes, and notes from the raw data.
- Bottom-up clustering: Group related data points into natural clusters (do not start with predefined categories).
- Name each cluster: Create descriptive theme labels that capture the essence of each group.
- Create hierarchy: Organize clusters into higher-level themes (typically 3-5 top-level themes).
- Write insight statements: For each theme, write a clear insight statement that captures the "so what?"
- Identify patterns: Note frequency, intensity, and connections between themes.
- Prioritize: Rank insights by impact on design decisions.
- 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
- After clustering, check that each participant appears at least once in the output — if any are absent, go back
- Patterns that appear in only one interview should be flagged as single-source, not discarded
This prevents the common LLM failure mode of building themes from the first one or two transcripts and fitting the rest retroactively.