claude-ux-auditlisted

# Claude UX audit ## Guards - If no UI files exist in the project (no JSX, TSX, Vue, Svelte, or HTML under `src/`), stop: `❌ No UI surfaces found to audit.` ## Step 1: read context Read these in parallel from the project root, skipping any that do not exist: - `CLAUDE.md`: project type and conventions - `.claude/DESIGN.md`: visual intent, tokens, typography, spacing rules - `.claude/wireframes/index.md` + every `.claude/wireframes/<surface>.md`: intended UI layout, UI copy, interaction rules. Surfaces are loaded one file at a time during Step 3. Per `standards/wireframes.md`, these carry layout and intent, not implementation detail. - `.claude/REQUIREMENTS.md`: feature scope and non-goals ## Step 2: identify surfaces List the UI surfaces in the project. A surface is a distinct screen, page, panel, or major component (e.g. sidepanel, popup, settings page, empty state). Group files by surface. Do not audit speculative or unfinished code flagged in `.claude/TASKS.md` as in-progress. ## Step 3: audit each surface For each surface, look for: 1. **Missing feedback states**: loading, empty, error, disabled, in-progress 2. **Unhandled edge cases**: long strings, overflow, zero items, many items, slow networks 3. **Inconsistencies**: spacing, tone of voice, interaction patterns, icon use, keyboard affordances 4. **Roughness in daily use**: friction, redundant steps, unclear affordances, ambiguous labels Use `.claude/DESIGN.md` and the per-surface `.claude/wireframes/<surfac