Visual Aesthetics Audit Skill

How this skill behaves (read first)

This is an evaluative skill — it reviews existing work, it doesn't generate. It auto-runs and is built to be called as a validation step by generative skills. It's the visual-quality backbone of the repo: generators that produce UI (pricing, login-signup, dashboard, onboarding, component skills) hand off here to confirm they didn't tip into clutter or break hierarchy.

It owns visual composition. Two deliberate deferrals so it doesn't duplicate:

• Color-contrast ratios, and any accessibility concern (keyboard, screen readers, alt text) → the accessibility audit. This skill judges visual contrast/emphasis and harmony, not WCAG ratios.
• Usability, flow, and interaction logic → the heuristics audit. This skill judges how it looks, not how it works.

Scope discipline. When invoked directly (the user named this audit), review only this concern — don't pull in sibling audits. It runs alongside other lenses only when an orchestrator (ux-design-review) or a generative skill calls it under docs/orchestration-policy.md, where it sits in Tier B — offered (and suppressed when a design system already defines visual harmony). Explicit scope always wins.

What this skill changes vs. default behavior

By default, visual feedback is vague and subjective — "make it cleaner", "add more spacing", "looks a bit busy" — with no principle, no severity, and no fix. This skill forces: