ux-ui
Skill1 starsChanged 6 days agoMITView on GitHub
Use when designing, specifying, or reviewing user interfaces and user experience for any product: layout, interaction, accessibility, and usability requirements; augments web-specific UX flow design or audits (web-ux) and HTML/CSS implementation (web-frontend).
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
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 15
Every interactive element MUST define all states: default, hover/focus, active, disabled, loading, error, and empty.
- Distinctive: line 24
Follow platform and industry conventions (Jakob's Law).
- Distinctive: line 28
Ask only what the task needs.
“Common” is measured: kept by at least 6 in 10 of the 3 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
UX/UI Requirements and Best Practices
Method
- Define the primary user tasks first; measure success by completion rate, time, and errors.
- Validate with real users or analytics; label untested conclusions as heuristic.
- Review against Nielsen's 10 heuristics: visible system status, real-world language, user control and exits, consistency, error prevention, recognition over recall, efficiency shortcuts, minimalism, plain-language error recovery, searchable task-focused help.
Non-negotiable requirements
- Accessibility MUST meet WCAG 2.2 AA: contrast >= 4.5:1 for normal text and >= 3:1 for large text and UI components; targets >= 24x24 CSS px (44 px comfortable); full keyboard operability; visible focus; never convey meaning by color alone.
- Every interactive element MUST define all states: default, hover/focus, active, disabled, loading, error, and empty.
- Feedback MUST arrive within 100 ms; show progress for waits over 1 s.
- Error messages MUST use plain language, appear beside the cause, and suggest a fix; never discard user input.
- Destructive actions MUST be recoverable; prefer undo over confirmation dialogs.
Layout and hierarchy
- One primary action per view; order content by attention: value and primary action first, proof near the decision, reference last.
- Group related items by Gestalt principles (proximity, similarity, common region); build hierarchy with scale, weight, and spacing before color.
- Minimize choices per decision (Hick's Law); make frequent targets large and close (Fitts's Law).
- Follow platform and industry conventions (Jakob's Law); deviate only with measured justification.
- Disclose complexity progressively; prefill, default, and remember safely.
Forms and content
- Ask only what the task needs; validate inline; name buttons by outcome ("Save changes", not "OK").
- Speak the user's language; front-load labels; no internal jargon or error codes.
Performance and responsiveness
- Perceived speed is UX: target LCP < 2.5 s, use skeleton screens over spinners, and design responsive layouts across viewport sizes, touch-first on mobile.
Reviews
- Report location, violated principle, affected task, severity, evidence, and specific fix, ordered by user impact.
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- jnotsknab/mux-swarm★ 9same name
- davidvornholt/mail-mcp★ 2same name
- davidvornholt/mailbox★ 2same 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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-prompt-authoringSkill
- ai-skill-authoringSkill
- ai-tool-writingSkill
- analyzing-securitySkill
- coreSkill
- language-writingSkill
- programming-api-designSkill
- programming-debuggingSkill
- programming-javascriptSkill
- programming-optimizationSkill
- technical-specificationsSkill
- web-buildSkill
- web-frontendSkill
- web-uxSkill
- web-visual-checkSkill
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.