agentleFS
mejbaurbaharmejbaurbahar/software-tester-skills/skills/usability-testing/SKILL.md

usability-testing

Skill1 starsChanged 52 days agoMITView on GitHub

Use when evaluating usability, user friction, UI clarity, and workflow ergonomics — Nielsen Norman heuristics, form validation feedback, error recovery paths, cognitive load, and accessibility overlap.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do long operations provide cancel options and ETA?

    line 19

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Usability & UX Testing

Overview

Usability testing evaluates how intuitive, efficient, and error-tolerant an application is for real human users. It identifies friction points, ambiguous affordances, and confusing error handling.

Nielsen Norman 10 Usability Heuristics Checklist

  1. Visibility of System Status:
    • Are loading spinners, progress bars, and operation states clearly communicated?
    • Do long operations provide cancel options and ETA?
  2. Match Between System and Real World:
    • Are labels, terms, and icons familiar to the target user audience (no developer jargon/stack traces)?
  3. User Control and Freedom:
    • Is there a clear undo/cancel mechanism for destructive actions (e.g. deletion modal, confirmation dialog)?
    • Can users back out of a multi-step modal without losing uncommitted input unexpectedly?
  4. Consistency and Standards:
    • Are button styles, icon meanings, and terminology consistent across all screens?
  5. Error Prevention:
    • Are destructive buttons visually distinct (e.g. red, separated from confirm)?
    • Are sensible constraints applied to input fields before form submission?
  6. Recognition Rather Than Recall:
    • Are instructions and contextual help visible when needed without requiring memorization?
  7. Flexibility and Efficiency of Use:
    • Are keyboard shortcuts, tab navigation, and search auto-completes supported?
  8. Aesthetic and Minimalist Design:
    • Is visual hierarchy clear? Is irrelevant or rarely needed information minimized?
  9. Help Users Recognize, Diagnose, and Recover from Errors:
    • Are error messages written in plain language indicating the exact cause and clear next steps?
    • Are specific input fields with errors highlighted inline with clear guidance?
  10. Help and Documentation:
    • Is contextual help easy to find, searchable, and focused on concrete user tasks?

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.