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 solid design system reference with clear constraints using MUST/SHOULD/NEVER language and specific values in well-formatted tables. Its main weaknesses are the lack of executable code examples showing how to implement these constraints (e.g., Tailwind classes, CSS snippets, or component code), some redundancy in reference data, and the monolithic structure that could benefit from splitting detailed reference tables into separate files.
Suggestions
Add executable code examples for key patterns - e.g., a Tailwind/CSS snippet for a button component, a card layout, or a heading style that demonstrates the design tokens in practice.
Split detailed reference tables (full typography list, spacing scale, border-radius scale) into a separate REFERENCE.md file, keeping only the most essential tokens and constraints in the main SKILL.md.
Complete the Components section with more than just one Ghost button variant - the current table is too sparse to be useful for building actual interfaces.
Add a brief 'How to apply' section at the top showing the priority order of constraints and how to verify compliance with the design system.
| 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., border-radius scale listed twice, typography reference repeating font family info, detected layout patterns with minimal value). Some sections like the text styles table with 10 rows of similar entries could be tightened. | 2 / 3 |
Actionability | Provides specific values (hex codes, pixel sizes, font weights) and clear constraints (MUST/SHOULD/NEVER), which is good for a design system skill. However, it lacks executable code examples - no CSS/Tailwind snippets, no component implementation examples, and the button component table has only one variant with mostly empty fields. The guidance is concrete in values but incomplete in implementation. | 2 / 3 |
Workflow Clarity | This is primarily a reference/constraint skill rather than a multi-step workflow, so explicit sequencing is less critical. However, there's no guidance on how to apply these constraints in order of priority, no validation steps for checking compliance, and no process for resolving conflicts between constraints. For a design system skill, a brief 'how to apply' workflow would improve clarity. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and tables, making it scannable. However, at ~150 lines with detailed reference tables (typography, colors, spacing), some of this reference material could be split into separate files. The skill tries to be both a quick reference and a comprehensive specification in one file, which makes it longer than ideal for a SKILL.md overview. | 2 / 3 |
Total | 8 / 12 Passed |