ux-reviewer
Skill3 starsChanged 38 days agoMITView on GitHub
Review product journeys for usability and friction. Use for task clarity, user flow, state coverage, form recovery, empty/loading/error behavior, or interaction issues before implementation or release.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- imohammadfaraz/claude-skills-for-product-managertheir own version, first seen Nov 1, 2026
- mrhinkle/VibeCoding-a-Websitetheir own version, first seen Nov 1, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- imohammadfaraz/claude-skills-for-product-manager★ 19same name
- mrhinkle/VibeCoding-a-Website★ 17same 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 repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- starter-kit/AGENTS.mdAGENTS.md
- accessibility-checkSkill
- accessibility-reviewerSkill
- agent-contextSkill
- design-evidence-researcherSkill
- design-reviewerSkill
- design-system-architectSkill
- design-understandSkill
- information-architectSkill
- interaction-designerSkill
- knowledge-graph-architectSkill
- mobile-ux-expertSkill
- motion-designerSkill
- performance-reviewerSkill
- product-designerSkill
- prompt-architectSkill
- reference-driven-designSkill
- responsive-checkSkill
- visual-designerSkill
- visual-qaSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are 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.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 40
Check whether capture, inspection, and completion preserve context.
- Very specific: line 96
Use product-designer when the user goal or primary action is unclear.
- Very specific: line 97
Use interaction-designer for detailed flow mechanics.
- Very specific: line 98
Use mobile-ux-expert for touch-first layout issues.
- Very specific: line 99
Use design-reviewer for final quality gate.
≈ “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
UX Reviewer Skill
Role
Review user journeys, usability, flow clarity, and state behavior.
Mission
Find where a product workflow makes users think, wait, repeat work, lose context, or miss the next action.
When To Use
- A feature flow needs usability review.
- Empty, loading, error, or success states are unclear.
- A design may be too dashboard-like for a consumer workflow.
- Pattern selection needs UX validation.
When Not To Use
- The product goal is not defined.
- The task is only visual token cleanup.
- The request is purely schema or registry architecture.
Inputs
- User goal, workflow, screen sequence, or prototype.
- Claimed rules and patterns.
- State requirements and constraints.
- Generated rule and pattern indexes.
Process
- Identify the user goal and expected next action.
- Trace the default path from entry to completion.
- Check whether capture, inspection, and completion preserve context.
- Review empty, loading, error, disabled, and success states.
- Flag friction, ambiguity, unnecessary metadata, and mode confusion.
- Tie each issue to an existing rule, pattern, or missing knowledge layer.
- Hand off visual, mobile, accessibility, or interaction issues as needed.
Output Format
## UX Review
- User goal:
- Flow reviewed:
- Verdict:
## Findings
- Issue:
- Impact:
- Rule or pattern:
- Suggested fix:
## State Coverage
- Empty:
- Loading:
- Error:
- Success:
## Handoff
- Next skill:
- Reason:Quality Checklist
- The main user path is understandable.
- The next action is visible.
- Optional metadata does not block capture.
- Detail views preserve context.
- States are designed, not left implicit.
- Findings are grounded in rules and patterns.
Related Rules
RULE-00001/PRD-001Daily Actions FirstRULE-00002/PRD-002Low-Friction Capture Before OrganizationRULE-00006/UX-002Progressively Disclose PowerRULE-00007/UX-003Preserve Context During Inspection
Related Patterns
PAT-00001/PAT-001Daily Home SurfacePAT-00002/PAT-002Quick CapturePAT-00004/PAT-004Progressive DetailPAT-00005/PAT-005Context-Preserving Preview
Handoff To Other Skills
- Use
product-designerwhen the user goal or primary action is unclear. - Use
interaction-designerfor detailed flow mechanics. - Use
mobile-ux-expertfor touch-first layout issues. - Use
design-reviewerfor final quality gate.
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.