usability-test-plan
Design a usability study — research questions, methodology, participant criteria, metrics, and facilitation guide. Use when planning the study as a whole. For writing the task scenarios inside it, use `test-scenario` (prototyping-testing).
Works with
--- name: usability-test-plan description: Design a usability study — research questions, methodology, participant criteria, metrics, and facilitation guide. Use when planning the study as a whole. For writing the task scenarios inside it, use `test-scenario` (prototyping-testing). license: MIT --- # 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
More Testing skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
setup-pre-commit
mattpocock/skills
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

