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.
The body is a well-structured overview with concrete technical directives and an exemplary one-level-deep reference split into references/rule.md. It is held back by redundant templated sections (Check, Explain) and an intro sentence that re-explains a concept Claude already knows, plus a DevTools verification step that is named but never detailed.
Suggestions
Delete the redundant '## Check' section (it restates the first Quick Reference bullet) and the content-free '## Explain' section, whose instruction adds nothing beyond the intro sentence.
Drop or fold the opening sentence about standard images looking blurry on retina displays; Claude already knows this, and the 'why' already lives in references/rule.md.
Inline a minimal executable example under '## Fix' (a 3-line img srcset snippet) and specify the DevTools verification step (e.g., emulating device pixel ratio in Chrome DevTools and checking the Network tab for the @2x/@3x asset), rather than only deferring to the reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The intro "Standard images look blurry on retina displays (2x, 3x pixel density)" explains a concept Claude already knows, "## Check" ("Check if high-resolution images are provided for retina displays (2x, 3x)") duplicates the first Quick Reference bullet, and "## Explain" ("Explain how retina images ensure sharp visuals") is a content-free meta-instruction. Mostly efficient, but several sections could be trimmed. Not 4 because there are three distinct instances of unnecessary or redundant content rather than minor over-explanation. | 3 / 5 |
Actionability | "Use srcset with x descriptors for fixed-size images", "Use srcset with w descriptors for responsive images", and "use image-set() or media queries" give concrete, executable directives, and the Code Review section instructs to "Flag exact files or components where format choice, sizing, or loading behavior violates the rule". Not 5 because no code is inlined in the body and DevTools verification is named but never specified (it lives only in the reference file). | 4 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sections provide a rough sequence, and the Code Review section gives the primary workflow: review assets/markup/delivery configuration, flag exact files, and "describe how to confirm the fix in DevTools". Not 5 because how the Check/Fix/Explain sections relate to the Code Review protocol is implicit, and the DevTools verification checkpoint is referenced but unspecified. | 4 / 5 |
Progressive Disclosure | The body is a concise overview (Quick Reference bullets) with a clearly signaled, purpose-stated one-level reference: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`". The bundle matches this exactly: references/rule.md exists and contains the code examples and framework guidance (React, Next.js, Sharp) with no further nested references. Not 4 because the split, signaling, and actual file structure are all fully appropriate. | 5 / 5 |
Total | 16 / 20 Passed |