Content
65%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 genuinely actionable, threshold-specific guidance and an exemplary progressive-disclosure split to references/rule.md. Its weaknesses are redundancy across the Quick Reference, Check, and Fix sections (plus a motivational intro Claude does not need), and a batch-fix workflow with no validation step surfaced in the body, even though the reference file contains a Verification section that could be pointed to.
Suggestions
Remove the motivational intro and deduplicate guidance repeated across Quick Reference, Check, and Fix (e.g. the 80% quality and srcset advice) so each fact appears once.
Add a verification step at the end of the Fix workflow — e.g. 'Verify: re-check file sizes and rendered dimensions as described in the Verification section of references/rule.md' — since the fix is a batch operation.
Inline one short corrected <picture>/srcset markup example (or an explicit pointer to the Code Example section of references/rule.md) so the Fix steps have a concrete output shape.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The intro sentence ('Images typically account for 50%+ of page weight. Unoptimized images cause slow load times... frustrated users') motivates what Claude already knows, and format/quality/srcset/lazy-loading guidance is repeated across Quick Reference, Check, and Fix (e.g. '80% quality' appears twice, srcset guidance three times). This matches anchor 3 (mostly efficient but could be tightened) rather than 4, where over-explanation would be only minor. | 3 / 5 |
Actionability | Guidance is concrete and specific: 'srcset with 400w, 800w, 1200w, 1600w variants', 'File sizes are reasonable (< 200KB for photos, < 50KB for graphics)', '80% quality for photos, 60% for AVIF', 'images > 100px wide'. It stays at anchor 4 rather than 5 because the body contains no executable commands or corrected markup examples — those live only in references/rule.md. | 4 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sequence is clearly organized with numbered steps, but the Fix step is a batch operation (converting and re-compressing images across the codebase) with no validation or verification step in the body — the Verification section in references/rule.md is not surfaced. Per the batch-operation cap, this holds workflow clarity at anchor 3 rather than 4. | 3 / 5 |
Progressive Disclosure | The body is a concise ~30-line overview while 316 lines of implementation detail (code examples, framework examples, build tool integration, verification) are appropriately split into a real, one-level-deep references/rule.md, clearly signaled ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') with well-organized sections. This matches anchor 5. | 5 / 5 |
Total | 15 / 20 Passed |