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
- memi-design/design-skillstheir own version, first seen Nov 8, 2026
- toribryan/design-skillstheir own version, first seen Oct 25, 2026
- Geruyang/skillstheir own version, first seen Oct 15, 2026
- henrique-simoes/Istaratheir own version, first seen Sep 27, 2026
- stritar/skillstheir own version, first seen Sep 11, 2026
- Abdox-menara/guard-skillstheir own version, first seen Aug 24, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- henrique-simoes/Istara★ 15same name
- memi-design/design-skills★ 7same name
- Geruyang/skills★ 2same name
- toribryan/design-skills★ 1same name
- Abdox-menara/guard-skills★ 0same name
- stritar/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository98 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- 42crunch-api-security-testingSkill
- a-b-testingSkill
- acceptance-testingSkill
- accessibility-testingSkill
- ai-agent-evaluationSkill
- ai-code-securitySkill
- ai-ml-testingSkill
- analytics-tracking-testingSkill
- api-testingSkill
- authn-authz-testingSkill
- autonomous-qa-orchestrationSkill
- bdd-gherkin-testingSkill
- blockchain-smart-contract-testingSkill
- bug-reportingSkill
- chaos-resilience-testingSkill
- chatbot-voice-agent-testingSkill
- cicd-testingSkill
- cli-testingSkill
- cloud-infrastructure-testingSkill
- code-coverage-analysisSkill
- compatibility-testingSkill
- compliance-testingSkill
- concurrency-race-condition-testingSkill
- configuration-feature-flag-testingSkill
- contract-testingSkill
- cross-browser-testingSkill
- database-testingSkill
- data-migration-testingSkill
- data-pipeline-etl-testingSkill
- date-time-timezone-testingSkill
- desktop-app-testingSkill
- disaster-recovery-backup-testingSkill
- e2e-testingSkill
- email-notification-testingSkill
- event-driven-messaging-testingSkill
- exploratory-testingSkill
- flaky-test-managementSkill
- functional-testingSkill
- fuzz-testingSkill
- game-testingSkill
- graphql-testingSkill
- iac-container-security-testingSkill
- installation-upgrade-testingSkill
- integration-testingSkill
- iot-embedded-testingSkill
- llm-security-auditSkill
- llm-testingSkill
- localization-testingSkill
- manual-testingSkill
- mcp-testingSkill
- memory-leak-resource-testingSkill
- microservices-testingSkill
- mobile-testingSkill
- mutation-testingSkill
- observability-testingSkill
- payment-ecommerce-testingSkill
- performance-testingSkill
- production-monitoring-synthetic-testingSkill
- The first 60 shown.
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
- Distinctive: line 19
Do long operations provide cancel options and ETA?
“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.
Files
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
- Visibility of System Status:
- Are loading spinners, progress bars, and operation states clearly communicated?
- Do long operations provide cancel options and ETA?
- Match Between System and Real World:
- Are labels, terms, and icons familiar to the target user audience (no developer jargon/stack traces)?
- 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?
- Consistency and Standards:
- Are button styles, icon meanings, and terminology consistent across all screens?
- Error Prevention:
- Are destructive buttons visually distinct (e.g. red, separated from confirm)?
- Are sensible constraints applied to input fields before form submission?
- Recognition Rather Than Recall:
- Are instructions and contextual help visible when needed without requiring memorization?
- Flexibility and Efficiency of Use:
- Are keyboard shortcuts, tab navigation, and search auto-completes supported?
- Aesthetic and Minimalist Design:
- Is visual hierarchy clear? Is irrelevant or rarely needed information minimized?
- 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?
- Help and Documentation:
- Is contextual help easy to find, searchable, and focused on concrete user tasks?
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
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.

