dragoon0x/everything-design-taste

usability-testing-patterns

Usability test planning, task design, moderation techniques, and analysis frameworks.

First seen Jul 18, 2026

Installation

$ npx skills add dragoon0x/everything-design-taste --skill usability-testing-patterns

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dragoon0x/everything-design-taste · top by installs.

npx skills add dragoon0x/everything-design-taste

Browse all from dragoon0x/everything-design-taste

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,441 B
  • docs SUMMARY.md 119 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Usability Testing Patterns

Test Planning

Sample Size

  • 5 users find ~85% of usability issues.
  • 8-12 for quantitative confidence.
  • Test with your target audience, not colleagues.

Task Design

  • Scenario-based: "You want to send money to a friend who just bought you lunch."
  • Not instruction-based: "Click the Send Money button in the top right."
  • 5-7 tasks per session (30-45 minute sessions).
  • Order from simple to complex.

Moderation

Questions to Ask

  • "What are you thinking right now?"
  • "What do you expect to happen?"
  • "Is this what you expected?"
  • "On a scale of 1-5, how easy was that?"

Questions to Avoid

  • "Did you find that easy?" (leading)
  • "Would you use this feature?" (hypothetical, unreliable)
  • "Do you like the design?" (preference, not usability)

Rules

  1. Don't help. Let users struggle (that's data).
  2. Don't explain the design. If it needs explanation, it needs redesign.
  3. Follow up with "why" after observing behavior.
  4. Record sessions (with consent).

Analysis

  • List all issues observed.
  • Rate severity: critical (blocks task), major (causes confusion), minor (causes slight delay).
  • Group by theme.
  • Prioritize fixes by severity × frequency.