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 with clear constraint language (MUST/SHOULD/NEVER) and specific values organized into logical sections. Its main weaknesses are the lack of executable code examples (no CSS, Tailwind, or component snippets) and the monolithic structure that could benefit from splitting detailed reference tables into separate files. Some sections contain redundant or low-value information (e.g., count columns, detected layout dimensions) that could be trimmed.
Suggestions
Add concrete 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 use.
Split detailed reference tables (full text styles, layout patterns) into a separate REFERENCE.md file, keeping only the most essential tokens and rules in the main SKILL.md.
Remove low-value data like the 'Count' column in text styles, 'used 21x' annotations, and the detected layout dimensions that don't translate to actionable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints, but includes some redundant information like the 'Count' column in text styles (all showing '1'), the 'used 21x' note for Inter, and detected layout patterns that add bulk without clear actionability. The typography reference section partially duplicates the text styles table. | 2 / 3 |
Actionability | Provides specific values (hex codes, pixel sizes, border radii) and clear constraint language (MUST/SHOULD/NEVER), which is good. However, it lacks executable code examples - no CSS snippets, no Tailwind classes, no component code. For a UI design system skill, concrete implementation examples (e.g., a button component, a card layout) would significantly improve actionability. | 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 Vercel-style UIs) is unambiguous. The 'When to Apply' section clearly scopes usage, and constraints are organized by domain (colors, typography, spacing, etc.) making them easy to follow. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and tables, but it's a fairly long monolithic document (~150 lines of detailed specifications). The extensive text styles table and layout patterns could be split into separate reference files, with SKILL.md providing a concise overview and linking out to detailed specs. | 2 / 3 |
Total | 9 / 12 Passed |