Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured design system constraint file that efficiently communicates rules using MUST/SHOULD/NEVER conventions. Its main weaknesses are incomplete sections (font families list is empty, Components section is empty), lack of executable code examples showing how to implement these constraints, and missed opportunities for progressive disclosure into sub-files for a richer design system reference.
Suggestions
Complete the incomplete sections: the font families constraint is missing its value list, and the Components section is empty
Add at least one concrete code example (e.g., a Tailwind CSS button component) demonstrating how multiple constraints combine in practice
Consider splitting detailed sections (interactive states, animation rules) into referenced sub-files to keep the main SKILL.md as a concise overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured. It uses MUST/SHOULD/NEVER constraints without over-explaining concepts Claude already knows. Every line provides specific, actionable design tokens or rules. | 3 / 3 |
Actionability | The skill provides specific values (hex codes, pixel values, CSS properties) which is good, but lacks executable code examples. For a UI design system skill, concrete component code snippets (e.g., a Tailwind/CSS example of a button with correct states) would significantly improve actionability. The font families section is incomplete ('MUST limit font families to:' with nothing listed). | 2 / 3 |
Workflow Clarity | This is a reference/constraint skill rather than a multi-step workflow, so the clear categorical organization (Colors, Typography, Spacing, etc.) with unambiguous rules serves as sufficient workflow guidance. The interactive states section clearly sequences focus, hover, and disabled states with specific values. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a semantic token table, but it's all inline in a single file. For a design system skill, separating component examples, color palettes, or animation guidelines into referenced files would improve navigation. The Components section is empty, suggesting incomplete content. | 2 / 3 |
Total | 10 / 12 Passed |