Design token audit
Agentic agent skills for the Quieto Tokens design token CLI. Each skill wraps a CLI command into a conversational workflow invocable via slash command.
npx -y skills add dillonschultz93/quieto-skills --skill design-token-auditAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Inspect and health-check an existing design token system. Runs orphan detection, broken reference checks, naming validation, and WCAG contrast analysis, then summarizes findings. Use when the user wants to audit, lint, or validate their token system quality.
SKILL.md
2.4 KB, as published. Nobody here has run it
Design Token Audit
You are helping the user audit their design token system for quality issues.
Prerequisites
Verify a token system exists in the current directory:
ls quieto.config.json tokens/
If no quieto.config.json or tokens/ directory exists, tell the user to run /design-token-init first.
Workflow
1. Run the inspect command
npx quieto-tokens inspect
This performs four analyses:
- Orphan detection: primitive tokens not referenced by any semantic token
- Broken references: semantic/component tokens pointing to non-existent primitives
- Naming validation: tokens that violate the DTCG naming conventions
- WCAG contrast analysis: foreground/background semantic color pairs checked against AA thresholds
2. Optionally write a markdown report
If the user wants a persistent report:
npx quieto-tokens inspect --output report.md
Then read and summarize the report:
cat report.md
3. Interpret results
Present findings to the user organized by severity:
Critical (must fix):
- Broken references — these will cause build failures or
undefinedCSS values - WCAG contrast failures — accessibility violations
Warning (should fix):
- Orphaned primitives — unused tokens bloat the system
- Naming violations — inconsistency makes tokens harder to discover
4. Suggest fixes
For each issue category, suggest concrete actions:
- Broken references: identify which semantic token has the bad ref and what it should point to. Check if a primitive was renamed or removed.
- Contrast failures: suggest alternative step pairings from the color ramp that would pass AA. Use the formula: contrast ratio >= 4.5:1 for normal text, >= 3:1 for large text.
- Orphans: determine if the primitive should be wired into a semantic role or removed.
- Naming violations: show the expected naming pattern from the project's nomenclature (see
docs/qds/design-tokens-nomenclature.md).
5. After fixing
If you help the user fix issues, re-run the audit to confirm a clean bill of health:
npx quieto-tokens inspect