design-system-boss
Installation
SKILL.md
Design system boss
A router. Read the app, match one playbook, copy its steps into .design-system/state.md word for word, and run them. A step you drop stays in the list as skipped (<reason>). Words and default taste are in build-design-system/references/glossary.md and build-design-system/references/taste.md. The person's words, AGENTS.md or CLAUDE.md and saved memory win over everything here.
Triggers
| The ask or the state | Playbook |
|---|---|
| A named screen or flow, "check before I ship" | playbooks/review.md |
| One component | playbooks/component.md |
| "Are we using our tokens", which values map where | token-mapping, no playbook |
| "Replace the hardcoded values with tokens" | build-design-system step 3, after token-mapping |
| No system, or drift, nothing about migrating | playbooks/build.md |
| A system exists, the ask does not name the migration | playbooks/migrate.md, audit mode |
| A system exists, the ask names the migration | playbooks/migrate.md, full mode |
An installed system is the source of truth, so no playbook seeds or builds over it. The state wins when it disagrees with the ask, and the report says so. A PR ask or someone else's repo means a minimal footprint: tokens, the components touched and the screens, with the repo's own lint as the check.