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 system reference with specific values and clear constraint language (MUST/SHOULD/NEVER), which is valuable. However, it reads more like raw design token extraction output than a curated, actionable skill — several values appear to be artifacts (0px input height, inconsistent element widths), there are no code examples showing implementation, and the document could be more concise by separating detailed reference tables from core guidelines.
Suggestions
Add executable code examples showing how to implement the design system (e.g., Tailwind config, CSS custom properties setup, or a sample component)
Review and clean up apparent extraction artifacts: '0px' input height, raw 'Detected Layout Patterns' dimensions, and duplicate 'body-secondary' entries with different values
Split detailed reference tables (full text styles list, all font sizes) into a separate REFERENCE.md and keep SKILL.md as a concise overview with the most important constraints and links
Add a brief workflow section explaining how to apply these constraints when building a new UI component (e.g., start with layout grid, apply typography tokens, then colors)
| 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, duplicate 'body-secondary' entries, 'Detected Layout Patterns' with raw pixel dimensions that feel like unprocessed data rather than actionable guidance). The '0px height for input fields' is suspicious and likely an extraction artifact rather than intentional design. | 2 / 3 |
Actionability | Provides specific values (hex codes, pixel sizes, font weights) and clear constraint rules (MUST/SHOULD/NEVER), which is good. However, there are no executable code examples showing how to implement these in CSS/Tailwind/any framework, no component code snippets, and some values seem like raw extraction artifacts (e.g., input height '0px', element widths '91px, 58px, 32px') rather than actionable design decisions. | 2 / 3 |
Workflow Clarity | This is primarily a reference/constraint document rather than a multi-step workflow, so explicit sequencing is less critical. However, there's no guidance on the order of applying these constraints when building a UI, no validation steps to check compliance, and no process for resolving conflicts between rules. 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 easy to scan. However, it's a fairly long monolithic document that could benefit from splitting detailed reference tables (all font sizes, all text styles) into separate reference files while keeping the SKILL.md as a concise overview with links. | 2 / 3 |
Total | 8 / 12 Passed |