File contents Design System Checker
When to activate
User runs /check-design-system or requests verification that a component uses design tokens and adheres to the design system.
When NOT to use
Full component audits (use /component-auditor instead)
Storybook generation (use /storybook-generator instead)
Accessibility reviews (use /review-a11y instead)
Instructions
Analyze token usage
Identify all hardcoded colors, spacing, typography
Map to design token equivalents
Flag any missing tokens in the design system
Suggest token structure if design system is incomplete
Check design system alignment
Component naming matches design system spec
Props align with design tokens (color, size, spacing, etc.)
Variants match approved design system variants
Dark mode support (if design system requires)
Review Storybook integration
Component exported to Storybook
All variants documented
Props documented with descriptions
Usage examples provided
Generate token migration plan
List hardcoded values to replace
Provide var() CSS or token references
Suggest code diffs for refactor
Estimate effort (small/medium/large)
Verify design spec alignment
Component matches Figma/design spec
Breakpoints and responsive behavior correct
Spacing, typography, colors all match
Interaction patterns (hover, focus, active) match
Produce audit report
Token compliance score (%)
Design system alignment score (%)
Storybook coverage score (%)
Actionable refactoring plan
Example
User: "Check if this Card component follows our design system."
Response:
Token Compliance: 60% (hardcoded colors, missing spacing tokens)
Design System Alignment: 90% (naming correct, variants match)
Storybook Coverage: 70% (missing dark mode variant)
Refactor Plan:
Replace color: #FF6B6B with var(--color-red-500)
Replace padding: 16px with var(--spacing-4)
Add dark mode variant to Storybook
Add aria-label for icon cards
1 --- 2 name: design-system-checker 3 description: Design System Checker 4 metadata: 5 source: https://skillmd.com/skills/uitbreidenos/design-system-checker 6 --- 7 # Design System Checker 8 9 ## When to activate 10 11 User runs `/check-design-system` or requests verification that a component uses design tokens and adheres to the design system. 12 13 ## When NOT to use 14 15 - Full component audits (use `/component-auditor` instead) 16 - Storybook generation (use `/storybook-generator` instead) 17 - Accessibility reviews (use `/review-a11y` instead) 18 19 ## Instructions 20 21 1. **Analyze token usage** 22 - Identify all hardcoded colors, spacing, typography 23 - Map to design token equivalents 24 - Flag any missing tokens in the design system 25 - Suggest token structure if design system is incomplete 26 27 2. **Check design system alignment** 28 - Component naming matches design system spec 29 - Props align with design tokens (color, size, spacing, etc.) 30 - Variants match approved design system variants 31 - Dark mode support (if design system requires) 32 33 3. **Review Storybook integration** 34 - Component exported to Storybook 35 - All variants documented 36 - Props documented with descriptions 37 - Usage examples provided 38 39 4. **Generate token migration plan** 40 - List hardcoded values to replace 41 - Provide `var()` CSS or token references 42 - Suggest code diffs for refactor 43 - Estimate effort (small/medium/large) 44 45 5. **Verify design spec alignment** 46 - Component matches Figma/design spec 47 - Breakpoints and responsive behavior correct 48 - Spacing, typography, colors all match 49 - Interaction patterns (hover, focus, active) match 50 51 6. **Produce audit report** 52 - Token compliance score (%) 53 - Design system alignment score (%) 54 - Storybook coverage score (%) 55 - Actionable refactoring plan 56 57 ## Example 58 59 User: "Check if this Card component follows our design system." 60 61 Response: 62 - **Token Compliance:** 60% (hardcoded colors, missing spacing tokens) 63 - **Design System Alignment:** 90% (naming correct, variants match) 64 - **Storybook Coverage:** 70% (missing dark mode variant) 65 - **Refactor Plan:** 66 - Replace `color: #FF6B6B` with `var(--color-red-500)` 67 - Replace `padding: 16px` with `var(--spacing-4)` 68 - Add dark mode variant to Storybook 69 - Add `aria-label` for icon cards
UitbreidenOS/UitKit commit 53201dc389
Frequently asked questions How do I install the Design System Checker skill? Run npx get-skill add uitbreidenos/design-system-checker in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
What does the Design System Checker skill do? Design System Checker It is listed under Design & Media on SkillMD.
Is Design System Checker safe to use? This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
Which AI agents work with Design System Checker? This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Is Design System Checker free to use? Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
Who published Design System Checker? UitbreidenOS (@uitbreidenos) published this skill. Their other Agent Skills are listed on their SkillMD profile.