token-auditlisted

# token-audit Scan CSS files for hardcoded values that should use design tokens, and report violations. ## When invoked Use this skill when asked to check for hardcoded values, audit token usage, find raw colours or pixel values, or check design system compliance — phrases like "check for hardcoded values", "token audit", "are there any raw colours", "audit [component] CSS". ## What is already automated `scripts/validate-token-usage.mjs` already fails the build on any `var(--…)` reference to a custom property nothing defines, so unresolvable-token references need no hand-check; this skill hunts for raw values that never reference a token at all. ## Instructions 1. **Determine scope.** Accept one of: - A specific component name (e.g. `Avatar`) → scans `src/components/Avatar/Avatar.css` - `all-components` → scans all `src/components/**/*.css` - `website` → scans all `website/src/**/*.css` (which includes the `.module.css` files) - A specific file path **The site background is outside every CSS scope, and deliberately so.** Its blob colours are token *names* in `website/src/data/shader-background.json`, resolved at runtime and handed to the GPU — no CSS file names them, so a `website` scan will pass without ever looking at what actually picks the site-wide background palette. Do not hand-audit it: `scripts/validate-shader-background.mjs` already fails the build if any blob references a token that is not in the registry, which is a stronger guarantee than t