Content
75%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.
A strong router-style SKILL.md: executable commands, explicit gates, verified one-level references, and no padding with known concepts. The main deductions are redundancy across the three overlapping route tables and a few workflow steps that defer their mechanics without pointing at a concrete command.
Suggestions
Collapse the overlapping route tables (Phase 0, Layer A, Quick routes) into a single authoritative routing table plus one 'when to load something else' section — interaction, ambience, and print rows currently appear in up to three places.
For steps that defer mechanics, name the owning artifact inline (e.g., the exact tool or command for "generate 2-3 imagen concept drafts", or the exact sub-command in the referenced file) so each step is executable without re-reading the target reference.
State the /visual-qa validation pass inline as a numbered final step of the implementation workflow rather than only as an axiom and a table row, making the workflow's terminal checkpoint impossible to miss.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense, assumes Claude's competence, and teaches no known concepts — every line is a routing decision. It falls short of 5 because routing rules for interaction, ambience, and print work are repeated across three overlapping tables (Phase 0, Layer A, Quick routes), and the 'AI-slop / senior-designer bar' mandate is restated several times in slightly different words. | 4 / 5 |
Actionability | Concrete, copy-paste commands are present ("uv run $SKILL_DIR/scripts/perfection/lighthouse-audit.py https://localhost:3000", the ui-ux-db search CLI with flags and domain/stack lists), plus a numbered branching workflow and a STOP-and-ask path. It misses 5 because some steps defer without any command — e.g., "generate 2-3 imagen concept drafts" gives no invocation or tool pointer. | 4 / 5 |
Workflow Clarity | The sequence (route → read references → gates → DESIGN.md → implement → QA) is clear, with explicit checkpoints (Design System Gate, Primitive Showcase Gate, Research Log accountability) and audit discipline (production build, 3-5 runs, take the median). It stays at 4 because validation mechanics are largely delegated to referenced files (/visual-qa, README phases) rather than stated inline, and the Phase-0 table and the Design System Workflow branches overlap enough that a reader must reconcile two routing systems. | 4 / 5 |
Progressive Disclosure | This is genuinely a router: all referenced files exist in the bundle, are one level deep, and are clearly signaled with 'Read when' columns. Not 5 because the same routing rows are duplicated across three tables instead of split cleanly, and designpowers/README.md routes into a nested vendor corpus (vendor/skills/..., vendor/agents/...) that sits two-plus levels below SKILL.md. | 4 / 5 |
Total | 16 / 20 Passed |