ui-ux-quality
Skill1 starsChanged 54 days agoMITView on GitHub
Make product flows clear and recoverable: primary action and next step obvious, forms with clear labels, validation timing, actionable errors, preserved input on failure, consistent navigation and terminology, and no hidden or surprising destructive actions. Use for user flows, forms, navigation, onboarding, dialogs, and interaction design.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- alfonsusenrico/pakemtheir own version, first seen Oct 25, 2026
- AL-JANEF/janefskillsword for word, first seen Sep 19, 2026
Other versions2 projects use a version of this.
Word for word · 1
- AL-JANEF/janefskills★ 1100% same
Edited · 0
None found.
Wrote their own version · 1
- alfonsusenrico/pakem★ 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 repository25 other files it gives its agents.
- janefSkill
- forgeSkill
- accessibility-qualitySkill
- api-contractsSkill
- architecture-integritySkill
- context-efficiencySkill
- database-integritySkill
- delegation-disciplineSkill
- devops-reliabilitySkill
- documentation-integritySkill
- frontend-design-qualitySkill
- git-disciplineSkill
- implementation-qualitySkill
- performance-scalabilitySkill
- review-defect-firstSkill
- root-cause-debuggingSkill
- testing-verificationSkill
- auth-hardeningSkill
- secrets-guardSkill
- security-auditSkill
- security-loggingSkill
- skill-security-auditSkill
- threat-modelSkill
- variant-huntSkill
- vuln-auditSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 19
Keep navigation, terminology, and interaction patterns consistent with the rest of the product.
- Distinctive: line 21
Avoid hidden critical actions, ambiguous icons, hover-only affordances, and surprising destructive behavior.
- Distinctive: line 29
Verify first-use, empty, loading, failure, retry, permission-denied, and completion flows.
- Very specific: line 33
Prefer evidence from rendered flows and task completion over aesthetic opinion 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/UX Quality
Optimize for task clarity, confidence, error prevention, and recovery. The user should always know where they are, what happens next, and how to undo it.
Principles
- Make the primary action, current state, context, and next step obvious.
- Keep navigation, terminology, and interaction patterns consistent with the rest of the product.
- Minimize unnecessary steps without hiding important decisions or risk.
- Avoid hidden critical actions, ambiguous icons, hover-only affordances, and surprising destructive behavior. Destructive actions confirm, are reversible where possible, or are clearly labeled as irreversible.
Forms
Clear labels, sensible defaults, validation at the right moment (not on every keystroke, not only on submit), actionable error messages next to the field, and preserved input on recoverable failure. Never lose a user's work to a validation error.
Flows
Verify first-use, empty, loading, failure, retry, permission-denied, and completion flows. Each has a clear message and a clear next step.
Evidence
Prefer evidence from rendered flows and task completion over aesthetic opinion alone. Compose with frontend-design-quality for visual implementation and accessibility-quality for keyboard and assistive-technology behavior.
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.