design-system-audit

# Audit the system, not one screen A **ramp** is the allowed value ladder; an **off-ramp value** is hand-selected outside it; a **gate** is automated enforcement. A 2026-08-03 inventory found 300+ off-ramp values, but their cause was four gate holes: | Hole | Effect | |---|---| | lint saw bracket values only | 268 named Tailwind steps such as `text-sm` and `rounded-md` bypassed the ramp | | two central surfaces were warning-only with no warning cap | 66 violations blocked nothing | | a colour checker skipped a directory | raw colours had never been checked there | | one screen owned a parallel four-step ramp | 17 of 33 elements sat off the app-wide ramp | Fixing values without closing entry holes guarantees recurrence. `/design-audit` measures one finished DOM change; `/responsive-sweep` measures breakpoint bands; this skill asks whether the system is enforceable. ## Scope and requested action Use the scope returned by `pnpm design:route`, or the user's explicit audit scope. "Every" below refers to that scope, not every screen in the repository. An audit request produces findings and repair proposals. Apply repairs only when the task also authorizes them; the repair order below does not itself authorize edits. Report unmeasured areas rather than expanding the audit silently. ## 0. Read actual ramps Extract values from `app/globals.css`; do not audit from memory or a stale prose copy. ```bash grep -oE "\-\-text-[a-z-]+:\s*[0-9.]+px" app/globals.css | sort -u grep -oE "...