ux-standards
Skill4 starsChanged 32 days agoMITView on GitHub
Apply the UX and accessibility standards. Use when designing or changing any user interface, flow, form, navigation, empty/error/loading state, or when producing a mock or screenshot for review.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- brand-guidelinesSkill
- compliance-policySkill
- intent-templateSkill
- secure-api-reviewSkill
- security-policySkill
- ux-standardsSkill
- brand-guidelinesSkill
- compliance-policySkill
- intent-templateSkill
- secure-api-reviewSkill
- security-policySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Components: use <design system package> components.
- Distinctive: line 17
States: every screen defines loading, empty, error and success states.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
UX and accessibility standards
Owner: <UX lead> · Source of truth: <link to the design system> · Version: <x.y>
<!-- TEMPLATE: replace with your standards. -->Must
- Accessibility: meet
<WCAG 2.2 AA>: keyboard reachable, visible focus, labels on every input, contrast from design tokens, no information conveyed by colour alone. - Components: use
<design system package>components; no bespoke replacements for existing ones. - States: every screen defines loading, empty, error and success states.
- Forms: inline validation, errors next to the field, never clear user input on error.
- Responsive: works from
<320px>wide; no horizontal scrolling. - Performance:
<e.g. LCP < 2.5s on mid-range mobile>.
Verifying UI work
Screenshot the result at <breakpoints> and compare it with the approved mock. Iterate until
it matches; two or three rounds is normal.
Output
In spec.md, list the flows and states affected. Conflicts with brand or compliance rules
go under Areas of concern, addressed to the owners involved.
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.

