Build or audit a design system including component library, design tokens, naming conventions, contribution model, and documentation.
SkillScore74Maintained
Automatic
◆Design & UX Review pack
Last verified 8/20/2026
What it changes
Passed 17 of 23 test cases with the skill, and 15 of 23 without it.
Without skill65%
With skill74%
Checks it passed that the model alone missed
Specifies design-system-audit.md as the output filename
Recommends a two-tier token model separating base values from semantic tokens
Identifies unverified asset metrics as missing data gaps rather than fabricating override statistics
3 fixed14 passed either way5 still failing1 broke
Pass-rate lift
+9 pp
Tokens
+65%
Agent turns
0%
Response time
-10%
Model gemini-3.6-flashMeasured 8/20/2026v217 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
We need a formal design system audit output file for the Acme Cloud console. What specific file name and mandatory sections should be used to document the findings?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies design-system-audit.md as the output filename
Missed
Passed
Includes gap analysis in the report structure
Passed
Passed
case-09 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md200 lines4 files
Design System
Build, evolve, or audit a design system. Stack-agnostic in principle. Implementation is stack-specific (Figma, Storybook, code library, etc.) but the structure and governance principles transfer.
This skill is for building the system. For applying a system to specific pages or components, use design-standards. For brand visual identity, use brand-identity.
When to use
Building a design system from scratch
Auditing an existing system for gaps or fragmentation
Defining design tokens at the system level
Structuring a component library
Establishing contribution and governance models
Migrating from ad-hoc components to a documented system
When NOT to use
Designing a single page or component (use design-standards)
Plan, manage, and optimize a domain portfolio. Use this skill for DNS architecture decisions, redirect strategies, registrar choice, parking unused domains, multi-site setups, and domain consolidation or split planning. Triggers on DNS, domain, registrar, redirect, parking, subdomain, apex, www vs non-www, multi-site, portfolio, hreflang setup, domain migration. Also triggers when planning a new site that needs domain decisions made before launch.