Content
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive design token reference with clear MUST/SHOULD/NEVER constraints, which is valuable for maintaining consistency. However, it reads more like a raw design audit output than a curated skill - it includes suspicious values (0px input height, inconsistent element widths), lacks executable code examples (CSS/Tailwind snippets), and could be more concise by separating reference data from core guidelines. The actionability would significantly improve with concrete code examples showing how to implement these tokens.
Suggestions
Add executable code examples (CSS custom properties, Tailwind config, or component snippets) showing how to implement the design tokens - e.g., a CSS variables block or a Tailwind theme extension.
Review and fix suspicious values: '0px' input height and 'consistent element widths: 16px, 13px, 17px, 18px, 10px' appear to be raw audit artifacts rather than intentional design decisions.
Split the detailed reference tables (full typography list, all font sizes) into a separate REFERENCE.md file, keeping only the core tokens and rules in the main skill.
Add a brief workflow or checklist for applying the design system when building a new component (e.g., 'Start with surface-base background → Apply Inter font → Use 4px grid → Verify contrast ratios').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with clear tables and MUST/SHOULD/NEVER constraints, but includes some redundancy (e.g., 'Border Radius Reference' section repeats what's already in the Borders section, duplicate 'body-secondary' entries, and the 'Detected Layout Patterns' section adds little value). The extensive typography table with individual 'Count: 1' entries feels like raw audit data rather than curated guidance. | 2 / 3 |
Actionability | The skill provides specific values (hex codes, pixel sizes, font weights) which is concrete, but lacks executable code examples. For a UI design system skill, there are no CSS/Tailwind snippets, no component code examples, and some values seem suspect (e.g., input height of '0px', element widths of '16px, 13px, 17px' which seem like raw measurements rather than actionable guidance). The MUST/SHOULD/NEVER format is clear but not always copy-paste ready. | 2 / 3 |
Workflow Clarity | The skill is organized as a reference rather than a workflow, which is appropriate for a design system. However, there's no guidance on how to apply these constraints in sequence when building a component, and no validation steps (e.g., how to verify contrast ratios meet the 4.5:1 requirement). The 'When to Apply' section is helpful but minimal. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, but it's a monolithic document that could benefit from splitting detailed reference tables (typography, colors) into separate files. There are no references to external files for deeper content, and some sections (like the full font size list) could be in a reference file rather than inline. | 2 / 3 |
Total | 8 / 12 Passed |