← ClaudeAtlas

ux-usability-studylisted

Plans and produces the complete set of materials for a moderated usability test — research questions and success metrics, a recruiting screener, a consent form, a facilitator script with think-aloud protocol, realistic task scenarios, a note-taking and issue-tracking structure, and a findings report. Use this whenever the user wants to run, plan, prepare, or moderate usability testing, user testing, or a usability study; wants to recruit or screen test participants; needs a test script, tasks, or scenarios; needs to take structured notes during sessions; or wants to synthesize observations from real user/participant sessions into prioritized findings (that synthesis belongs here, not to heuristic evaluation). Trigger even when the user only describes the situation ("we're about to watch five people use our checkout flow") without naming "usability testing" explicitly.
JoaoMonteiro100/ux-design-skills · ★ 0 · Web & Frontend · score 67
Install: claude install-skill JoaoMonteiro100/ux-design-skills
# UX Usability Study Kit This skill helps you run a **moderated usability study** end to end: figure out what you're trying to learn, recruit the right people, prepare everything you say and hand to a participant, take notes you can actually use, and turn raw observations into findings a team will act on. A usability test is simple in spirit — you give real, representative people realistic tasks and watch where the product helps or fails them — but it goes wrong in predictable ways: fuzzy goals, the wrong participants, leading questions, tasks that hand users the answer, and notes that can't be synthesized afterward. The guidance below exists to avoid those failure modes, not to impose ceremony. Scale it to the study: a scrappy five-person test of one flow needs a fraction of what a formal benchmark study needs. ## How to work through a study Usability work is a pipeline, and each artifact feeds the next — success metrics shape the screener, the screener shapes recruiting, the tasks come from the research questions, and the note structure comes from the tasks. So don't jump straight to writing a script. Establish the foundation first, then generate the downstream materials from it. Ask the user which pieces they need. Most people want either the **full kit** or one specific artifact ("just write me a screener"). If they want one piece, still ground it in the foundation questions below — a screener written without knowing who the target user is will be generic and useless