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.
A well-structured overview with excellent progressive disclosure into a real, content-rich reference file, but the body itself is padded with tautological Check/Explain sections and lacks any executable guidance or explicit verification checkpoints of its own.
Suggestions
Cut redundancy: remove the duplicated 60-80% statistic and replace the tautological Check ("Analyze if images are properly compressed...") and Explain sections with distinct, useful content or fold them into Quick Reference.
Add one copy-paste-ready command to the Fix section (e.g. a one-liner like `convert input.jpg -quality 80 output.jpg` or `npx sharp-cli input.jpg -o output.webp --quality 80`) so the body handles the common case without opening the reference.
Make the workflow explicit and verifiable: order the Check → Fix → Verify phases and spell out the DevTools confirmation steps (Lighthouse "Efficiently encode images" audit, Network tab file sizes) instead of just alluding to DevTools.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and free of concept-explaining filler, but contains redundant padding: the 60-80% reduction stat appears twice ("Can reduce file sizes by 60-80% without visible quality loss" and "Explain how proper compression can reduce image sizes by 60-80%"), and the Check section ("Analyze if images are properly compressed without significant quality loss") merely restates the title. | 3 / 5 |
Actionability | The Quick Reference gives concrete parameters ("Compress JPEG to 70-85% quality", "lossy compression for photos, lossless for graphics") and names tools, but the Fix section ("Compress images using tools like ImageOptim, TinyPNG, or automated build processes") offers only high-level hints with no executable command in the body — all runnable code is deferred to references/rule.md. This lands between minimal guidance and mostly-executable guidance. | 3 / 5 |
Workflow Clarity | Check → Fix → Explain → Code Review provides a recognizable phase sequence, but the phases are parallel headings rather than an ordered workflow, and validation is only implicit: "describe how to confirm the fix in DevTools" names no concrete checkpoint steps (the actual verification steps live only in the reference file). | 3 / 5 |
Progressive Disclosure | The body is a lean, well-sectioned overview (~45 lines) with a clearly signaled, one-level-deep pointer — "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — and that file exists and delivers exactly what is promised (ImageMagick/sharp commands, Webpack/Vite configs, verification steps). | 5 / 5 |
Total | 14 / 20 Passed |