ui-auditlisted

# UI audit Two jobs: keep `criteria.md` current with what visual quality means for *this* app, then judge the running UI against it and drive it toward something people genuinely enjoy looking at — beautiful, polished, characterful — **within the brand**. **Read `.claude/skills/audit/audit-loop.md` first** — it owns the loop (research gating, the critique test, how criteria change, the report format, and the rule that findings only become issues with the user's approval). This file owns the domain: what "good-looking" means here and how to see it truthfully. Pass `--research` to force a research pass; otherwise the cadence in `criteria.md` decides (90 days). ## The three fences (internalize these before anything else) Everything this skill does lives inside three lines it must not cross. They are the whole reason it can be trusted to touch a live product's look: 1. **Visual, never UX.** In scope: colour, layout, spacing, type, depth, radii/borders, iconography, imagery treatment, motion-as-polish, empty-state *visuals*. Out of scope: flows, step order, information architecture, navigation, what a control *does*, and copy/wording. Test: *does the fix change what the user sees, or what the user does?* Only the first is yours (U-R03). **This fence bounds the kind of change, not its size:** recomposing the *same* content — its size, weight, placement, framing, backdrop — is visual and in scope however dramatic the visual difference; changing *which*