design-system-checklisted
Install: claude install-skill product-llc/claude-skills
# Design-system check — measured, not judged
A design-system audit has two halves. The first is measurement: what the contract defines, how much of the interface refers to it, and where the interface has escaped it. The second is judgment: which escapes are defects, which are deliberate, and which unused tokens are dead versus reserved. This skill does the first half exactly and does not pretend to do the second. Whether an escape matters depends on what the team meant by it, and you have not met the team.
Method by Alex Zapadenko: https://www.product.inc/notes/design-system-audit-cost. Free to use, change and redistribute.
## Rules that hold throughout
- Every number you report comes from a script you ran. Quote the command next to the number so it can be re-run; when one script prints many numbers, a per-key print flag satisfies this. Never estimate a count and never tally by reading. Reading is for correcting a matcher, and every correction is declared beside the number it changed.
- Never modify the product. No token added, no class fixed, no config touched, no commits. The check is read-only. If a token the code needs does not exist, that is a finding, not a task.
- Matching is exact, not heuristic. A token contract is a finite list of names; expand it into the finite set of strings the code can use to reach it, and match those. A regex that "probably" catches colours is a finding-generator you will then have to apologise for.
- Say what each number is a count of. "F