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 has strong bones — concrete Check and Fix guidance and an exemplary progressive-disclosure split to references/rule.md — but it is dragged down by triple-repeated statistics, a redundant Explain section of concepts Claude already knows, and no validation checkpoint in a batch fix workflow.
Suggestions
Merge the Quick Reference and Explain sections into one: the same web.dev statistics (25-35% smaller, 40-50% smaller, 97% support) currently appear three times in the intro, Quick Reference, and Explain.
Add an inline validation step to the Fix workflow (e.g., verify converted file size and visual quality, and confirm the JPEG fallback still loads in Safari) since the Fix is a batch operation across all images — the verification content in references/rule.md should be surfaced as a step in the body.
Drop the Explain section's generic compression background and time-sensitive version details ('Chrome 85+', 'Firefox 93+', 'as of 2024') or move them to references/rule.md — Claude already knows WebP/AVIF basics, and dated version numbers go stale.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Noticeably verbose with several padded sections: the same web.dev size statistics (25-35%, 40-50%, 97% support) appear three times across the intro, Quick Reference, and Explain; the Explain section instructs Claude to explain WebP/AVIF compression basics it already knows and carries time-sensitive version numbers ('Chrome 85+', 'as of 2024') outside any deprecated section; and the Code Review section restates the description. The core Check/Fix sections are tight, keeping this above anchor 1. | 2 / 5 |
Actionability | Check and Fix give concrete, executable guidance: 'Convert to WebP at 80% quality using Squoosh or Sharp', specific <picture>/<source> markup structure, an @supports CSS pattern, and findings reported with 'file path and line number'. Minor gap: no copy-paste code block in the body itself (those live in references/rule.md). | 4 / 5 |
Workflow Clarity | A clear Check → Fix sequence with numbered, specific steps, but the Fix is a batch operation (converting every image and rewriting markup across the codebase) with no inline validation checkpoint — only the vague 'describe how to confirm the fix in DevTools'. Per the batch-operation rule, workflow clarity is capped at 3. | 3 / 5 |
Progressive Disclosure | A ~45-line overview body with a well-signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') that exists and contains exactly the promised code examples, conversion script, framework guidance, and verification steps. Content is appropriately split between overview and reference. | 5 / 5 |
Total | 14 / 20 Passed |