ui-usability-acceptance
Skill2 starsChanged 4 months agoMITView on GitHub
Accept or reject CodeFlowMu UI changes based on usability evidence. Use when QA, PM, or UI reviewer needs desktop/mobile checks, interaction results, visual overlap checks, and FCoP semantic correctness.
In this repository42 other files it gives its agents.
- architect-boundary-reviewSkill
- architect-decision-recordSkill
- architect-system-designSkill
- browser-playwright-checkSkill
- browser-useSkill
- code-search-navigationSkill
- controlled-emergence-observerSkill
- dev-code-locationSkill
- dev-small-scope-patchSkill
- dev-test-and-explainSkill
- eval-observation-writingSkill
- eval-promotion-adviceSkill
- eval-risk-gap-analysisSkill
- ops-log-diagnosisSkill
- ops-runtime-healthSkill
- ops-stuck-workflowSkill
- pm-acceptance-criteriaSkill
- pm-architecture-reviewSkill
- pm-delivery-planSkill
- pm-evolve-skillsSkill
- pm-long-horizon-planningSkill
- pm-priority-triageSkill
- pm-product-design-briefSkill
- pm-product-requirementsSkill
- pm-scope-controlSkill
- pm-solve-problemsSkill
- pm-tech-scopeSkill
- qa-regression-checkSkill
- qa-reproduce-issueSkill
- qa-verify-fixSkill
- run-local-command-checkSkill
- test-selectionSkill
- tm-delivery-governanceSkill
- tm-review-routingSkill
- tm-risk-dependencySkill
- ui-information-architectureSkill
- ui-requirementsSkill
- ui-visual-consistencySkill
- web-extractSkill
- web-researchSkill
- web-searchSkill
- windows-useSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
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 10
Use after UI implementation or when reviewing a UI report.
- Distinctive: line 14
Check the workflow, not just screenshots.
- Distinctive: line 15
Verify desktop and mobile where relevant.
- Distinctive: line 25
Do not accept untested interactions.
- Distinctive: line 26
Do not ignore mobile overlap.
- Distinctive: line 27
Do not archive or approve lifecycle from UI review alone.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
UI Usability Acceptance
When to use
Use after UI implementation or when reviewing a UI report.
Rules
- Check the workflow, not just screenshots.
- Verify desktop and mobile where relevant.
- Record interaction results and evidence.
- Reject UI that misstates lifecycle, task, report, or review state.
Required output
Use docs/skills/ui-playbook/usability-acceptance.md.
Forbidden actions
- Do not accept untested interactions.
- Do not ignore mobile overlap.
- Do not archive or approve lifecycle from UI review alone.
Minimal example
Viewport: 390x844
Interaction: open report details
Result: pass
Evidence: screenshot pathDoes 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.