Content
85%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 a well-structured router: it sequences work clearly with explicit validation gates and delegates detail to a verified, one-level-deep reference bundle. Its main weakness is minor rhetorical repetition of the core axiom and actionability that is partly mediated through referenced files rather than inline executable steps.
Suggestions
Consolidate the 'design + perfection load together / both win or neither' principle into one location (e.g., shared axioms) and reference it from Phase 0 and the workflow to reduce repetition.
For the most common workflows (clone-from-url, image-to-code, lazyweb), include a one-line inline executable snippet or a single concrete example so the body is actionable before the reference is opened.
Define or note the $SKILL_DIR convention once near the first CLI block so the copy-paste commands are self-contained.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and directive, assuming Claude's competence without explaining known concepts, but repeats the design+perfection 'both win or neither' axiom across Phase 0, the workflow, and shared axioms — minor instances that could be trimmed. | 4 / 5 |
Actionability | Provides copy-paste CLI commands (lighthouse-audit.py, search.py) and exact file-load routing tables, but delegates the executable procedures for clone/image-to-code/lazyweb/interaction to referenced files, leaving minor gaps in the body itself. | 4 / 5 |
Workflow Clarity | Clear sequence (Phase 0 route → branch selection → implementation → QA) with explicit validation gates (/visual-qa reference-fidelity, Primitive Showcase Gate), a feedback loop ('until the dual-oracle completion gate passes on fresh evidence'), and a Research Log checklist. | 5 / 5 |
Progressive Disclosure | The body is an overview/router pointing to one-level-deep references (all verified present), organized via routing tables and _INDEX.md, with detailed material appropriately split into references/ — clear navigation, no deep nesting. | 5 / 5 |
Total | 18 / 20 Passed |