Content
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable design system specification with concrete values, specific constraints, and clear component definitions. Its main weaknesses are the lack of validation/verification steps in the workflow (no way to check compliance with the banned elements list or spec adherence) and the monolithic structure that could benefit from splitting detailed specs into referenced files. Minor verbosity in introductory/explanatory text could be trimmed.
Suggestions
Add a validation checklist at the end of the execution protocol (e.g., 'Verify: no banned fonts used, no shadows above 0.05 opacity, no banned words in copy, all borders match #EAEAEA spec').
Split detailed component specifications (Section 5), color palette (Section 4), and animation specs (Section 7) into separate referenced files to improve progressive disclosure.
Remove the Protocol Overview description paragraph in Section 1—it restates what the skill already demonstrates through its specifications and adds no actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly detailed and well-organized, but includes some unnecessary verbosity—like the full protocol overview/description section and explanatory phrases ('Color is a scarce resource') that Claude doesn't need. Some sections could be tightened (e.g., the negative constraints list includes rationale that's implicit). However, most content is specification-level detail that earns its place. | 2 / 3 |
Actionability | The skill provides highly specific, concrete values throughout: exact hex codes, exact CSS properties, exact font stacks, exact Tailwind classes, exact animation curves and durations, exact border-radius values, and specific icon library names. The execution protocol in section 8 gives a clear step-by-step build order. This is copy-paste ready specification. | 3 / 3 |
Workflow Clarity | Section 8 provides a reasonable sequential execution protocol (establish whitespace → constrain width → apply typography → borders → animations → depth). However, there are no validation checkpoints or feedback loops—no step to verify the output matches the spec, no checklist to confirm banned elements aren't present, and no error recovery guidance. For a design system that could produce non-compliant output, validation steps would be valuable. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear numbered sections and sub-headings, making it scannable. However, at ~120+ lines of dense specification, some content (like the full color palette, component specs, or animation details) could be split into referenced files. As a standalone SKILL.md with no bundle, it's a monolithic but organized document that would benefit from splitting. | 2 / 3 |
Total | 9 / 12 Passed |