Content
57%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 overview with exemplary progressive disclosure — a single verified, clearly signaled reference file holding the implementation detail. It is weakened by near-contentless Check/Explain sections that restate the title, a Fix section with no executable command, and no validation step in the body for what is a batch operation.
Suggestions
Make the Fix section executable: replace 'Compress images using tools like ImageOptim, TinyPNG, or automated build processes' with a copy-paste-ready command (e.g., a one-line ImageMagick or sharp-cli invocation) or explicitly point to the commands in references/rule.md.
Tighten redundancy: merge the Check and Explain one-liners, which restate the title and Quick Reference, or replace them with what to do when the check fails.
Add a body-level verification step (e.g., 'Confirm via DevTools Network tab or Lighthouse efficiently-encode-images audit') so the batch compression workflow has an explicit validation checkpoint instead of it living only in references/rule.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean, but the intro 'Uncompressed images are often 5-10x larger than needed' is background Claude already knows, and the Check ('Analyze if images are properly compressed') and Explain ('Explain how proper compression can reduce image sizes by 60-80%') sections mostly restate the title and Quick Reference, so the body could be tightened. | 3 / 5 |
Actionability | The Quick Reference gives concrete numbers ('Compress JPEG to 70-85% quality', 'lossy for photos, lossless for graphics'), but the Fix section only names tools ('ImageOptim, TinyPNG') with no commands, and all executable code is deferred to references/rule.md, leaving the body itself without executable guidance. | 3 / 5 |
Workflow Clarity | A rough Check → Fix → Explain → Code Review sequence is present, but each step is a one-line directive with no validation checkpoints; since image compression is a batch-style operation and the body omits any verification step (it lives only in the reference file), workflow clarity is capped at 3. | 3 / 5 |
Progressive Disclosure | The ~35-line body is a clear overview that appropriately splits implementation detail into the single, well-signaled, one-level-deep references/rule.md ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), which exists and contains the deferred code examples. | 5 / 5 |
Total | 14 / 20 Passed |