From nickcrew-claude-ctx-plugin
Conducts multi-perspective UX reviews using Nielsen heuristics, WCAG accessibility checks, and interaction analysis for UI components, user flows, PRs, and design critiques.
npx claudepluginhub nickcrew/claude-cortexThis skill uses the workspace's default tool permissions.
Comprehensive user experience review that coordinates usability, accessibility, and interaction design perspectives for thorough analysis of components, flows, or features.
Reviews UX/UI for usability and accessibility using Nielsen's heuristics, WCAG 2.1 guidelines, user flow analysis, cognitive load, and form evaluation. Use for pre-release audits and compliance checks.
Evaluates UX/UI of websites, apps, and digital interfaces using Jakob Nielsen's 10 usability heuristics. Identifies issues in visibility of status, system-real-world match, consistency, error prevention, flexibility, aesthetics, recognition, error recovery, and documentation.
Evaluates user interfaces using Nielsen's 10 usability heuristics to identify violations like poor system status visibility, inconsistency, and error-prone designs. Reports severity, location, and fixes for UX reviews.
Share bugs, ideas, or general feedback.
Comprehensive user experience review that coordinates usability, accessibility, and interaction design perspectives for thorough analysis of components, flows, or features.
ui-design-aesthetics insteadAnswer these questions before reviewing:
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? |
<!-- 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>
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 |
## 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
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