Content
71%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, actionable review workflow with concrete thresholds, tooling, and an exemplary one-level-deep reference split. The main cost is redundancy: the bandwidth-waste rationale is repeated across the intro, Quick Reference, and Explain sections (with an internally inconsistent "4x the data" figure), and the body's verification step is gestured at rather than specified.
Suggestions
Consolidate the bandwidth-waste rationale into one place (e.g., keep only the Explain section) and fix the inconsistent math — the intro's "downloads 4x the data" contradicts the pixel-scaling figures (~16x, ~25x) used in Quick Reference and Explain.
Make the verification checkpoint explicit in the body, e.g., a short "Verify" step after Fix naming how to confirm in DevTools (compare rendered vs intrinsic width in the Network/Elements panel) instead of only "describe how to confirm the fix in DevTools".
Trim the intro paragraph to one or two sentences of motivation; the Lighthouse-audit context already appears in Quick Reference, so the duplicate mention can be cut.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body explains why oversized images waste bandwidth in three places — the intro paragraph ("serving a 1600px image downloads 4x the data users need"), Quick Reference bullet 1 ("wastes ~16x the necessary bandwidth"), and the Explain section ("bandwidth scales with pixel count, not linear dimensions") — a concept Claude already knows. The intro's "4x the data" claim is also inconsistent with the pixel-scaling figures (16x, 25x) used elsewhere, so tightening would both save tokens and remove the contradiction; this fits anchor 3 rather than anchor 4's minor trims. | 3 / 5 |
Actionability | The Check and Fix sections give concrete, mostly executable guidance with specific thresholds ("more than 2x the rendered width", "images over 200px wide should have srcset variants"), named tools ("use Sharp or Squoosh"), exact variant widths ("400w, 800w, 1200w, 1600w"), and an inline sizes example. It stops short of anchor 5's copy-paste-ready code in the body — the actual HTML examples are deferred to references/rule.md — leaving minor gaps. | 4 / 5 |
Workflow Clarity | A clear Check → Fix → Explain → Code Review sequence, with numbered steps inside Check and Fix and a verification cue ("describe how to confirm the fix in DevTools"; rule.md has Automated/Manual Checks). It matches anchor 4 rather than anchor 5 because the body's verification is mentioned but not spelled out — no explicit validate-then-iterate checkpoint in the body itself. | 4 / 5 |
Progressive Disclosure | The ~34-line body is a well-organized overview (Quick Reference, Check, Fix, Explain, Code Review) that appropriately pushes full code examples and framework-specific guidance to a single, clearly signaled, one-level-deep reference — "see `references/rule.md`" — which exists and contains no nested references. This matches anchor 5: clear overview, well-signaled shallow reference, easy navigation. | 5 / 5 |
Total | 16 / 20 Passed |