Content
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is highly actionable with concrete code and specs, but it is far too verbose — re-teaching fundamental design knowledge Claude already has — and its progressive-disclosure references point to bundle files that are absent. The design workflow is sequenced but lacks a real validation feedback loop.
Suggestions
Cut the tutorial-level explanations of concepts Claude already knows (typography line-height/line-length rules, color theory, WCAG ratios, Nielsen/Norman UX principles, responsive basics) and keep only the skill's distinctive opinionated guidance (banned fonts/colors, tone extremes, the ask-then-commit protocol).
Create the referenced bundle files (MOTION-SPEC.md, ACCESSIBILITY.md, RESPONSIVE-DESIGN.md) so the inline "see MOTION-SPEC.md" reference and the Progressive Disclosure Files list are not broken links, and move the large color/typography/layout reference material into them.
Add an explicit validate→fix→retry feedback loop to the design workflow (e.g. after playwright MCP / accessibility checks fail, list the fix-and-revalidate steps) so the workflow has a real checkpoint rather than a single terminal validate step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~700-line body re-explains concepts Claude already knows (typography line-height/line-length/tracking rules, color theory, WCAG contrast ratios, Nielsen/Norman UX principles like "Direct Manipulation" and "Forgiveness", responsive basics), matching the verbose/explains-known-concepts anchor. | 1 / 3 |
Actionability | Provides executable, copy-paste-ready code (e.g. `import { Button } from "@/components/ui/button"`, `font-size: clamp(2rem, 5vw, 4rem)`) and concrete numeric specs (44×44px touch targets, 4.5:1 contrast, full font scale), satisfying the fully-executable anchor. | 3 / 3 |
Workflow Clarity | The 4-step Design Workflow plus Validate step (playwright MCP, accessibility checks) and checklists give a clear sequence, but there is no validate→fix→retry feedback loop, which the score-3 anchor requires, so it stays at 2. | 2 / 3 |
Progressive Disclosure | The body signals MOTION-SPEC.md inline and lists three "Progressive Disclosure Files", but none of those bundle files actually exist, and the document is a monolithic wall of text whose large color/typography/layout sections should be split out — fitting the has-structure-but-should-be-separated anchor. | 2 / 3 |
Total | 8 / 12 Passed |