review-uxlisted

# UX Review Be thorough but concise. **Use this when:** Evaluating user experience quality - usability, accessibility, user flows, and how the UI feels to use. **Don't use this when:** Testing a running web application in a browser (/review-browser). Reviewing code quality (/review-code), reviewing command prompts (/review-commands), checking plan completion (/review-plan), or doing a pre-release check (/review-full). **Important:** This command reviews artifacts - code, markup, specs, and screenshots. It does not evaluate a running application. When live interaction would be needed for a complete assessment, state that as a limitation in the summary. ## Critical Rules <rules> 1. **REPORT ONLY** - Do NOT make any changes or edits to files 2. **Wait for approval** - Only fix things after I say "fix it" 3. **Explain simply** - Use plain English, avoid jargon </rules> ## How to Review <procedure> Read the UI-related files (components, templates, styles, markup). Then pick one of two modes: **Small change** (1-2 files, minor UI tweak): Review in a single pass. No sub-agents needed. **Bigger change** (3+ files or new user-facing feature): Run four focused sub-agents in parallel using the Agent tool, then combine their results: | Sub-agent | What it checks | |-----------|----------------| | **Usability** | Nielsen's heuristics - feedback, user control, error prevention, consistent language | | **Accessibility** | WCAG AA - keyboard navigation, contrast, focus indicator