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 well-organized design system reference with clear constraint levels (MUST/SHOULD/NEVER) and concrete values. Its main weaknesses are the lack of executable code examples showing implementation, some redundant/low-value data (duplicate text style entries, repeated typography info), and the monolithic structure that could benefit from splitting reference tables into separate files.
Suggestions
Add at least one concrete code example (e.g., a React/Tailwind component) showing how to apply the design tokens and constraints together for a common UI element like a card or button.
Remove redundant sections like 'Typography Reference' that repeat information already in the Text Styles table, and consolidate the near-duplicate text style entries (e.g., multiple 'text-14px' rows with slightly different colors).
Consider splitting the detailed token tables (Semantic Tokens, Text Styles, Border Radius) into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with the key constraints and linking to the reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful design tokens and constraints, but includes redundant information (e.g., the text styles table has many near-duplicate entries with slightly different colors, the 'Typography Reference' section repeats what's already in the table, and detected layout patterns add little value). Some sections like 'Font Families: Inter (used 44x)' are noise. | 2 / 3 |
Actionability | The skill provides concrete values (hex codes, pixel sizes, specific CSS properties) which is good, but lacks executable code examples showing how to implement these patterns in actual components. The MUST/SHOULD/NEVER constraints are specific but would benefit from at least one concrete component implementation example (e.g., a Tailwind or CSS snippet for a button). | 2 / 3 |
Workflow Clarity | This is a reference/constraint skill rather than a multi-step workflow skill. The single task (apply design system constraints when building UI) is unambiguous, and the constraints are clearly organized by category with clear priority levels (MUST/SHOULD/NEVER). No destructive or batch operations are involved. | 3 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear section headers and tables, but it's a long monolithic file (~150+ lines of detailed reference data) that could benefit from splitting detailed token tables and text style references into separate files. No external references are provided for deeper exploration. | 2 / 3 |
Total | 9 / 12 Passed |