Content
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is well-structured as an overview with excellent progressive disclosure to references/rule.md, but it leans on generic guidance and restates known concepts, with no executable examples or validation checkpoints inline. It reads more as a rule checklist than an actionable, sequenced workflow.
Suggestions
Drop the opening paragraph and the "Explain" section that restate what unit tests are and why they matter—Claude already knows this—and keep only directive guidance to tighten conciseness.
Add at least one concrete, executable example inline (e.g., a minimal vitest test snippet or the `pnpm test:coverage` command with thresholds) instead of offloading all specifics to references/rule.md, so the body is actionable on its own.
Reframe Check → Fix → Code Review as an explicit sequenced workflow with a validation checkpoint, e.g., "run `pnpm test:coverage` and confirm thresholds pass before treating the rule as satisfied," to add the missing feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph ("Unit tests catch bugs before they reach production, serve as documentation...") and the "Explain" section restate concepts Claude already knows, but the remainder (Quick Reference, Check/Fix/Code Review) is lean, matching the score-2 "mostly efficient but includes some unnecessary explanation" anchor. | 2 / 3 |
Actionability | The Quick Reference bullets give some concrete guidance ("Aim for 80%+ coverage", "Mock external dependencies, not internal modules") but the body has no executable code or specific commands—all specifics are offloaded to references/rule.md—so guidance is incomplete per the score-2 anchor. | 2 / 3 |
Workflow Clarity | The Check/Fix/Explain/Code Review sections provide loose structure but no clear sequenced workflow and no explicit validation checkpoint in the body, fitting the score-2 "sequence present but checkpoints missing or implicit" anchor. | 2 / 3 |
Progressive Disclosure | The body is a concise overview that clearly signals a one-level-deep reference ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`", which exists), matching the score-3 "clear overview with well-signaled one-level-deep references" anchor. | 3 / 3 |
Total | 9 / 12 Passed |