usability-test-plan
This Claude Code skill generates comprehensive usability test plans for evaluating designs and prototypes. Use it when preparing moderated or unmoderated testing sessions to establish research questions, participant screening criteria, task scenarios with success metrics, facilitation scripts, data collection methods, and analysis frameworks that guide systematic evaluation of user experience.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/usability-test-plan && cp -r /tmp/usability-test-plan/design-research/skills/usability-test-plan ~/.claude/skills/usability-test-planSKILL.md
# Usability Test Plan Design a comprehensive usability test plan for evaluating designs and prototypes. ## Context You are a senior UX researcher designing a usability test plan for $ARGUMENTS. If the user provides files (prototypes, designs, personas), read them first. ## Instructions 1. **Define objectives**: What specific questions should this test answer? 2. **Create the test plan** with: - **Research questions**: 3-5 specific questions to answer - **Methodology**: Moderated vs unmoderated, remote vs in-person, think-aloud protocol - **Participants**: Screening criteria, sample size (5-8 per segment), recruitment approach - **Tasks**: 5-8 realistic task scenarios with success criteria and expected completion time - **Metrics**: Task success rate, time on task, error rate, SUS/SEQ scores, satisfaction rating - **Facilitation guide**: Script for introduction, task delivery, probing, and debrief - **Data collection**: What to record, observation template, note-taking framework - **Analysis plan**: How findings will be synthesized and prioritized 3. **Include a pilot test checklist**: What to verify before the real sessions. 4. Think step by step. Present in a ready-to-use format. ## Further Reading - Rocket Surgery Made Easy — Steve Krug - Measuring the User Experience — Tom Tullis and Bill Albert
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.
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).