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 strong actionable content: a concrete scan procedure, numbered fixes with an inline copy-paste onerror snippet, a verification method, and an appropriately deferred one-level reference for framework details. Its main weakness is token efficiency — the 'Explain' section and intro duplicate rationale Claude already knows, and the templated 'Code Review' section drifts into optimization concerns foreign to this rule.
Suggestions
Cut or merge the 'Explain' section: the 404/browser-behavior and LCP rationale duplicates the intro paragraph and covers concepts Claude already knows, so the tokens are better spent on the Check/Fix workflow.
Wire the DevTools blocked-request verification into the Fix workflow as an explicit post-fix checkpoint (e.g. 'After applying a fallback, block the image request in DevTools Network tab and confirm the placeholder renders') so the validate-fix-retest loop is a step, not a Quick Reference bullet.
Trim the 'Code Review' section's references to 'format choice, sizing, or loading behavior', which belong to image-optimization rules rather than broken-image detection, and focus it on flagging missing files and missing onerror handlers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The Quick Reference, Check, and Fix sections are tight and high-value, but the 'Explain' section re-explains 404 behavior, console errors, and LCP impact that Claude already knows and duplicates the intro paragraph, and the templated 'Code Review' section adds further padding. Not 4 because a whole section of over-explanation exceeds 'minor instances'; not 2 because the actionable core (~60% of the body) is genuinely lean with no library-tutorial filler. | 3 / 5 |
Actionability | Provides a copy-paste-ready snippet ('onerror="this.src='/images/fallback.png'; this.onerror=null;"'), a fully specified scan procedure with four concrete detection categories and a report format (file path and line number), and a concrete test method (DevTools Network tab blocked requests). Not 5 because the React/Vue ('implement an onError callback') and external-CDN ('consider downloading and self-hosting') cases are direction-level hints rather than executable guidance; not 3 because real executable code and complete procedures are present. | 4 / 5 |
Workflow Clarity | The Check-then-Fix sequence is clear, with numbered identification criteria (1-4) and numbered remediation steps (1-5), and an explicit verification technique ('Test with DevTools Network tab blocked requests to verify fallback behaviour'). Not 5 because verification is not wired into the flow as an ordered post-fix checkpoint with a retest loop; not 3 because the sequence and a concrete validation method are both explicitly present, not merely implicit. | 4 / 5 |
Progressive Disclosure | The ~30-line body is a clear overview with well-organized sections (Quick Reference, Check, Fix), and detailed implementation is split into a single, clearly signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') that exists in the bundle and holds the deferred code examples. This matches the anchor for a clear overview with well-signaled one-level references and easy navigation. | 5 / 5 |
Total | 16 / 20 Passed |