design-system-audit

<!-- Generated from `.claude/skills/_available/design/design-system-audit/SKILL.md` by `scripts/generate-agents-skills.py`. Do not edit. --> # Design-system audit ## When to use Use this skill when a named design system has a canonical component or token source and the requester can define the artifact sample and as-of boundary. It can assess adoption, coverage, repeated patterns, deviations, and documented exceptions without changing them. Do not use it to define a new system, refactor product work, approve an exception, or claim organization-wide adoption from an undeclared sample. Not for editing components, tokens, design files, code, or adoption records without a separately confirmed action. ## Inputs and source discipline - Identify the canonical component and token sources, version, source date, and as-of date/time. Record the rule that makes a component or token canonical; if the source is missing or contradictory, keep adoption unknown. - Declare the sample and coverage: population if known, eligibility rule, included and excluded artifacts, artifact/version dates, and inspection method. Do not call a sample representative without evidence for that claim. - Define adoption numerator and denominator before counting. Record the adoption source, source date, retrieval/as-of date, and items that are uncountable; never invent a denominator or percentage. - Locate exception records and their rationale, authority, version, and date. Treat a local pattern...