ux-review
Skill4 starsChanged 5 days agoMITView on GitHub
Review or audit existing user interfaces, UX journeys, screenshots, prototypes, or code for usability issues; produce evidence-graded, prioritized findings linked to Laws of UX and testable remediation.
26 other projects use a version of this.
Adopted by
Most recently taken up by
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- Come-In-Labs/agent-skillstheir own version, first seen Nov 15, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Nov 9, 2026
- whyashthakker/estacktheir own version, first seen Nov 8, 2026
- WilliamEbong/CourseForgetheir own version, first seen Nov 8, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
Other versions26 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 26
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- gitkraken/vscode-gitlens★ 10ksame name
- striderZA/OpenCodeGameStudios★ 118same name
- cenconq25/claude-code-app-studio★ 40same name
- brianwestphal/glassbox★ 34same name
- parhamb/design-skills★ 21same name
- dawn840705/codex-code-studios★ 17same name
- lilangMax/ClaudeCodeGameStudios★ 8same name
- RoleModel/skills★ 7same name
- hongyuanc/codex-game-studios★ 5same name
16 more not listed
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 repository55 other files it gives its agents.
- design-balance-and-proportionSkill
- design-brand-and-art-directionSkill
- design-buildSkill
- design-color-theorySkill
- design-diagnoseSkill
- design-hierarchy-and-emphasisSkill
- design-imagery-and-textureSkill
- design-layout-and-gridSkill
- design-movement-and-flowSkill
- design-reviewSkill
- design-rhythm-and-patternSkill
- design-typographySkill
- design-unity-and-systemsSkill
- design-validateSkill
- security-api-files-and-realtimeSkill
- security-authentication-and-sessionsSkill
- security-authorizationSkill
- security-browser-and-originSkill
- security-buildSkill
- security-configuration-and-secretsSkill
- security-crypto-and-dataSkill
- security-dependencies-and-buildSkill
- security-diagnoseSkill
- security-injection-and-validationSkill
- security-logging-and-failureSkill
- security-reviewSkill
- security-threat-model-and-designSkill
- security-validateSkill
- ux-accessibilitySkill
- ux-buildSkill
- ux-controls-and-inputsSkill
- ux-decisions-and-loadSkill
- ux-diagnoseSkill
- ux-feedback-and-performanceSkill
- ux-forms-and-errorsSkill
- ux-journeys-and-motivationSkill
- ux-navigation-and-structureSkill
- ux-onboarding-and-learningSkill
- ux-trust-and-ethicsSkill
- ux-validateSkill
- ux-visual-hierarchySkill
- wcag-alternatives-and-mediaSkill
- wcag-assistive-tech-and-statusSkill
- wcag-buildSkill
- wcag-diagnoseSkill
- wcag-forms-and-error-preventionSkill
- wcag-keyboard-and-focusSkill
- wcag-language-and-predictabilitySkill
- wcag-navigation-and-discoverySkill
- wcag-pointer-and-touchSkill
- wcag-reviewSkill
- wcag-semantics-and-reading-orderSkill
- wcag-time-and-motionSkill
- wcag-validateSkill
- wcag-visual-and-responsiveSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use for reviews, audits, critique and issue triage without assuming permission to change code.
- Very specific: line 12
Read references/evidence-and-priority.md when you need to grade evidence, resolve conflicting interpretations, or rank complex findings.
- Very specific: line 23
Default output: a short executive diagnosis, then an ordered issue table with ID, evidence, location, user impact, primary class, law, …
“Common” is measured: kept by at least 6 in 10 of the 24 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
Perform a user-centered UX review
Scope
Use for reviews, audits, critique and issue triage without assuming permission to change code.
Read references/evidence-and-priority.md when you need to grade evidence, resolve conflicting interpretations, or rank complex findings.
Procedure
- Identify audience, task goals, critical journeys, product constraints, responsive modes and available evidence. If artifacts exist, inspect them; don't guess from descriptions that conflict with artifacts.
- Walk the journey in goal order: entry, locate, decide, act, wait, errors/recovery, completion, return. For each observed failure, apply the taxonomy from
../ux-diagnose/references/issue_taxonomy.jsonand the relevant domain playbook. - Inspect cross-cutting accessibility, semantics, keyboard/motion, loading/error states and trust. Keep aesthetics separate from usability. Do not claim WCAG conformance from a screenshot.
- Report only substantiated or clearly marked hypothesized findings. Record exact screen/component or step and concrete expected-versus-actual behavior. Limit each finding to 1 primary class + up to 2 supporting laws when possible.
- Rank by user harm (including low-frequency severe harms), observed frequency, persistence and recovery cost. Separate fixes that remove the cause from visual patches.
- For each finding: proposed change, tradeoff, and a measurable/observable acceptance check. Offer quick wins and systemic changes without pretending untested suggestions are validated.
Default output: a short executive diagnosis, then an ordered issue table with ID, evidence, location, user impact, primary class, law, severity, confidence, fix, validation. Do not produce counts or decorative scores merely to signal thoroughness. If the user requested JSON, use the issue-record schema. Cite the exact law URL when relying on it.
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.