Content
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid design system reference skill with clear constraints using MUST/SHOULD/NEVER language and well-organized tables of design tokens. Its main weaknesses are the lack of executable code examples showing how to implement these constraints (e.g., CSS/Tailwind snippets or component examples), some auto-generated feeling content that could be curated more tightly, and the monolithic structure that could benefit from splitting detailed references into separate files.
Suggestions
Add at least 2-3 executable code examples (e.g., a Tailwind/CSS card component, a button variant, a heading) showing how to apply the design tokens in practice.
Remove auto-generated artifacts like 'currently 14 colors detected', 'used 15x', and 'Count' columns that don't add actionable value for Claude.
Consider splitting the detailed token tables (Text Styles, Semantic Tokens) into a separate TOKENS.md reference file, keeping only the most essential values inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints. However, there's some redundancy (e.g., border-radius scale listed twice, typography reference repeating info from the table) and some detected values that feel auto-generated rather than curated (e.g., 'currently 14 colors detected', 'used 15x', element widths '137px, 144px, 6px'). | 2 / 3 |
Actionability | The skill provides specific values (hex codes, pixel sizes, font weights) which are concrete and actionable for implementation. However, it lacks executable code examples—no CSS snippets, no Tailwind classes, no component code. For a UI design system skill, having at least one concrete implementation example (e.g., a button component or a card layout) would make it fully actionable. | 2 / 3 |
Workflow Clarity | This is a reference/constraint skill rather than a multi-step workflow skill. The single-purpose nature (apply these design tokens and rules when building UI) is unambiguous. The MUST/SHOULD/NEVER hierarchy provides clear priority ordering, and the 'When to Apply' section clearly scopes usage. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and tables, but it's quite long (~150 lines of dense reference material) and could benefit from splitting detailed token tables and typography references into separate files. There are no references to external files for deeper content, and some sections (like the full text styles table with 10 entries) could be externalized. | 2 / 3 |
Total | 9 / 12 Passed |