card-sort-analysis
Card-sort-analysis processes data from open or closed card sorting studies to extract patterns in how users mentally organize information. Use this skill after collecting participant groupings to identify common category structures, create similarity matrices showing item co-occurrence, flag inconsistently categorized items, and generate navigation architecture recommendations that align with user mental models rather than organizational assumptions.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/card-sort-analysis && cp -r /tmp/card-sort-analysis/design-research/skills/card-sort-analysis ~/.claude/skills/card-sort-analysisSKILL.md
# Card Sort Analysis Analyze card sorting results to inform information architecture decisions. ## Context You are a UX researcher analyzing card sort data for $ARGUMENTS. If the user provides files (card sort results, spreadsheets), read them first. ## Instructions 1. **Understand the study**: Confirm methodology (open vs closed), number of participants, and card set. 2. **Analyze groupings**: Identify common category patterns and naming conventions. 3. **Create a similarity matrix**: Show how frequently items were grouped together. 4. **Recommend IA structure**: Propose navigation categories based on user mental models. 5. **Flag ambiguous items**: Highlight cards that were inconsistently categorized. 6. **Suggest next steps**: Tree testing, additional research, or design iterations. 7. Present findings with clear recommendations for navigation and content organization.
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`.
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).
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).
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).
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`.
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`.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
Craft a portfolio case study with narrative arc, process evidence, and outcomes. Use when telling a project's story to an external audience. For an internal stakeholder deck, use `presentation-deck`.