Content
67%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is strongly actionable with concrete design guardrails, explicit validation checkpoints, and well-signaled one-level-deep references, but it carries significant removable scaffolding (SSL-primitive tables, scheduling boilerplate) and inconsistent resource organization. Trimming the meta-workflow sections and consolidating the duplicated resource listings would materially improve token efficiency.
Suggestions
Remove or collapse the 'Scheduling'/'Intent signature'/'Logical Operations' scaffolding (including the SSL-primitive table), which restates the workflow in non-operational jargon — the Scenes/Canonical path sections already cover it.
Consolidate the '### Resources' and '## References' lists into one section with a consistent directory name ('resources/' vs 'reference/' vs 'examples/' are currently mixed), and drop the inline Anti-Pattern Quick Reference since resources/anti-patterns.md already holds the full catalog.
Fix heading levels so Typography/Color/Layout/Motion/Components nest under the Anti-Pattern Quick Reference heading instead of sitting as siblings, and introduce the 7 phases before guardrail #1 references 'Phase 1 (Setup)'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Concrete content (exact font stacks, timing budgets, DO/DON'T lists) is diluted by meta-scaffolding that adds tokens without operational value, such as the 'Scheduling'/'Intent signature' boilerplate and the 'Logical Operations' table mapping actions to invented 'SSL primitives' (READ, INFER, CALL_TOOL). | 3 / 5 |
Actionability | Provides mostly executable guidance: exact system font stack, CJK font priority order, 375px minimum, 150ms/200-500ms/800ms motion budgets, a runnable `bunx getdesign@latest list` command, and a copy-pasteable '## Reference Sites' markdown snippet; minor gaps remain (no inline DESIGN.md template or shadcn install example). | 4 / 5 |
Workflow Clarity | Sequencing is explicit (PREPARE→FINALIZE scenes, canonical path, 7-phase summary) with a VERIFY phase and real feedback loops ('If accessibility checks fail, revise before handoff'; vendor-fetch retry/continue/abort with default), but three parallel restatements of the same workflow and a forward reference to 'Phase 1 (Setup)' before phases are introduced create minor ambiguity. | 4 / 5 |
Progressive Disclosure | Detailed material is appropriately split into clearly labeled, one-level-deep references with per-file descriptions, but the inline Anti-Pattern Quick Reference duplicates resources/anti-patterns.md, two separate resource lists use inconsistent directory names ('resources/' vs 'reference/'), and no bundle files are present in the skill directory to verify the referenced paths resolve. | 4 / 5 |
Total | 15 / 20 Passed |