Content
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a reasonably well-structured design system reference with clear constraint language (MUST/SHOULD/NEVER) and specific token values. Its main weaknesses are the lack of concrete implementation code examples, some internal contradictions (light-mode claim vs. black background), and verbose reference sections that could be externalized. The skill would benefit from executable code snippets showing how to apply these tokens in practice.
Suggestions
Add concrete code examples (e.g., Tailwind config, CSS custom properties, or React component snippets) showing how to implement the design tokens
Resolve the contradiction between 'light-mode interfaces' / 'light backgrounds' and surface-base being #000000 — clarify the intended design intent
Move detailed reference tables (full font size list, border radius scale) to a separate REFERENCE.md file and link to it from the main skill
Specify exact hover state colors instead of relative descriptions like 'lighten background by 10%'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints, but includes some redundancy (e.g., the Typography Reference section listing all font sizes adds bulk, and the full RGB values alongside HEX are arguably unnecessary for Claude). The detected layout patterns and some reference sections could be trimmed. | 2 / 3 |
Actionability | The skill provides specific values (colors, sizes, radii) and clear constraint rules (MUST/SHOULD/NEVER), which is good for a design system skill. However, it lacks concrete code examples showing how to implement these tokens in CSS/Tailwind/React, and some guidance is vague (e.g., 'lighten background by 10%' without specifying the resulting color). | 2 / 3 |
Workflow Clarity | For a design reference skill, there's no multi-step workflow needed, but the 'When to Apply' section is minimal and the organization of sections is clear. However, there's no guidance on how to validate that an implementation conforms to these constraints, and some contradictions exist (e.g., 'light-mode interfaces' and 'light backgrounds' but surface-base is #000000 black). | 2 / 3 |
Progressive Disclosure | The content is well-sectioned with clear headings and tables, making it scannable. However, the detailed reference tables (all font sizes, all border radii) could be split into separate reference files to keep the main skill leaner, and there are no cross-references to external files for deeper detail. | 2 / 3 |
Total | 8 / 12 Passed |