ux-review · nickcrew — Claude Code skill: what it does, how to install
ux-review reviews a component or flow from three angles: usability heuristics, WCAG 2.1 AA accessibility and interaction design. Comes back with a prioritized report.
MIT 119 installs ★ 71 updated 2026-06-29
npx skills add NickCrew/Claude-Cortex --skill ux-review -a claude-codeWhat ux-review does
The skill runs a review in five stages. The agent first pins down what the user is trying to do and where the component sits in the wider flow. Then it goes through Nielsen's 10 heuristics as a checklist. The same screen is looked at again from usability, WCAG 2.1 AA accessibility and interaction design angles.
--focus trims the scope. --focus=ux keeps task flow and error recovery, --focus=a11y takes keyboard access, contrast and focus management, --focus=interaction covers loading, empty and error states plus feedback timing. Findings are bucketed as Critical, High, Enhancement or Future and written up as a markdown report with a table per category. Purely visual critique is out of scope: the skill points to ui-design-aesthetics for that.
Everything sits in one SKILL.md, from the heuristic table to the report template.
What it helps with
- run a new component through Nielsen's heuristics before release
- check a form against WCAG 2.1 AA
- map a checkout flow and find where users get stuck
- sort review findings by urgency for the current sprint
- audit loading, empty and error states
Example prompts for the agent
- Run a UX review on
CheckoutForm.tsx: heuristics, accessibility, states. - Audit the signup flow for keyboard navigation and focus handling with
--focus=a11y. - Critique the account-deletion dialog and rank the findings by severity.
How to install ux-review
1Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill ux-review -a claude-code2Manually: put the files in place
~/.claude/skills/ux-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ux-review/
1Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill ux-review -a codex2Manually: put the files in place
.agents/skills/ux-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill ux-review -a cursor2Manually: put the files in place
.cursor/skills/ux-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install NickCrew/Claude-Cortex skills/ux-review2Manually: put the files in place
.github/skills/ux-review/SKILL.md1Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill ux-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/NickCrew/Claude-Cortex --path skills/ux-reviewManually: put the files in place
.devin/skills/ux-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill ux-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ux-review
How do I install ux-review in Claude Code?
Run npx skills add NickCrew/Claude-Cortex --skill ux-review -a claude-code. The skill file lands at ~/.claude/skills/ux-review/SKILL.md.
What does ux-review do?
It examines a component or flow against usability heuristics, checks WCAG 2.1 AA accessibility, and looks at how states and feedback are handled. The result is a markdown report with findings ordered by priority.
Can I limit the review to accessibility only?
Yes, pass --focus=a11y. The other scopes are --focus=ux and --focus=interaction.
Source text
SKILL.md · MIT
--- name: ux-review description: Multi-perspective UX review combining usability heuristics, WCAG accessibility checks, and interaction design analysis. Use when reviewing UI components before release, evaluating user flows for usability issues, conducting design critiques, or auditing accessibility compliance. tags: - ux - usability - accessibility - design-review - heuristics triggers: - ux review - usability review - design critique - user experience analysis - heuristic evaluation keywords: - UX review - usability review - accessibility audit - review --- # UX Review Comprehensive user experience review that coordinates usability, accessibility, and interaction design perspectives for thorough analysis of components, flows, or features. ## When to Use This Skill - Reviewing new components or features before release - Evaluating existing flows for usability issues - PR reviews that touch UI/UX code - Design system component reviews - Onboarding flow or checkout flow optimization - Avoid using for purely visual/aesthetic reviews — use `ui-design-aesthetics` instead ## Workflow ### Step 1: Gather Context Answer these questions before reviewing: 1. What is the user trying to accomplish? 2. What is this component's role in the larger flow? 3. Who are the target users (personas, skill level)? 4. What are the success criteria? ### Step 2: Run Heuristic Scan (Nielsen's 10) Evaluate the interface against each heuristic: | Heuristic | Check | |-----------|-------| | Visibility of system status | Does the user always know what's happening? | | Match with real world | Does it use familiar language and concepts? | | User control and freedom | Can users undo, go back, escape? | | Consistency and standards | Does it follow platform conventions? | | Error prevention | Are mistakes prevented before they happen? | | Recognition over recall | Is information visible rather than memorized? | | Flexibility and efficiency | Are there shortcuts for expert users? | | Aesthetic and minimalist design | Is every element necessary? | | Error recovery | Are error messages helpful and actionable? | | Help and documentation | Is guidance available when needed? | ### Step 3: Multi-Perspective Analysis #### Usability Perspective - **User flow**: Is the path to completion clear and efficient? - **Information architecture**: Is content organized logically? - **Cognitive load**: Is the interface overwhelming? - **Mental models**: Does it work like users expect? #### Accessibility Perspective (WCAG 2.1 AA) - **Keyboard navigation**: Can everything be done without a mouse? - **Screen reader**: Is the experience equivalent for assistive tech users? - **Color contrast**: Do all text/UI elements meet 4.5:1 ratio? - **Focus management**: Is focus order logical, visible, and never trapped? ```html <!-- Example: Accessible button with proper ARIA --> <button aria-label="Close dialog" aria-describedby="close-hint"> <svg aria-hidden="true"><!-- icon --></svg> </button> <span id="close-hint" class="sr-only">Press Escape to close</span> ``` #### Interaction Design Perspective - **State coverage**: Are all states handled (loading, empty, error, success)? - **Feedback**: Does the user know their action worked? - **Transitions**: Are animations purposeful and under 300ms? - **Progressive disclosure**: Is complexity revealed appropriately? ### Step 4: Prioritize Findings Categorize every finding: | Priority | Criteria | Action | |----------|----------|--------| | **Critical** | Blocks usability or fails WCAG AA | Must fix before release | | **High** | Significantly degrades experience | Fix in current sprint | | **Enhancement** | Improves delight and efficiency | Backlog for next iteration | | **Future** | Long-term improvements | Track in roadmap | ### Step 5: Produce Review Report ```markdown ## UX Review: [Component/Flow Name] ### Summary [2-3 sentence executive summary] ### Critical Issues - [ ] Issue 1: [Description, impact, WCAG criterion if applicable] - [ ] Issue 2: [Description, impact] ### Recommendations by Category #### Usability | Finding | Impact | Recommendation | |---------|--------|----------------| | [Issue] | High/Med/Low | [Fix] | #### Accessibility | Finding | WCAG Criterion | Recommendation | |---------|----------------|----------------| | [Issue] | [2.x.x Level] | [Fix] | #### Interaction Design | Finding | Impact | Recommendation | |---------|--------|----------------| | [Issue] | High/Med/Low | [Fix] | ### Next Steps 1. Create issues for critical findings 2. Add accessibility requirements to acceptance criteria 3. Schedule follow-up review after fixes ``` ## Focus Area Deep Dives Use `--focus` to narrow the review scope: - **`--focus=ux`**: User flow mapping, task efficiency, error recovery, learnability - **`--focus=a11y`**: WCAG 2.1 AA audit, keyboard nav, screen reader, contrast, focus management - **`--focus=interaction`**: State coverage, feedback timing, micro-interactions, animation review ## Best Practices - **Test with real content** — Lorem ipsum hides information architecture problems - **Check all states** — Empty, loading, error, success, and edge-case states - **Verify keyboard flow** — Tab through the entire component without a mouse - **Use browser dev tools** — Lighthouse accessibility audit catches low-hanging fruit - **Prioritize ruthlessly** — A focused list of critical fixes beats a wall of suggestions
© NickCrew · MIT · NickCrew/Claude-Cortex
Similar skills
All skills for Design →ux-review by other authors comes first.