Content
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a tidy overview that correctly defers detail to a single well-signaled reference file, but it lacks executable guidance in the body itself, repeats the compression stat, and provides no real validation checkpoints.
Suggestions
Move or consolidate the duplicated compression stats so the 50%/20% figures appear once; replace generic Check/Fix/Explain prose with specific, actionable steps.
Add a minimal executable example (e.g., a <picture> snippet with AVIF/WebP/JPEG sources) directly in the body rather than only in the reference.
Include an explicit verification checkpoint in the Code Review workflow (e.g., confirm format and size in DevTools Network/Performance panels) to sequence the review with validation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 50%-smaller-than-JPEG / 20%-smaller-than-WebP stat is repeated three times (intro, Quick Reference, Explain) and the Check/Fix sections are generic filler, so it is mostly efficient but includes redundant padding rather than fully lean. | 2 / 3 |
Actionability | The body describes rather than instructs ("Check if the website supports AVIF", "Implement AVIF support with proper fallbacks", "Explain how AVIF provides...") with no executable code or commands — concrete examples are deferred to the reference file, matching the vague/abstract anchor. | 1 / 3 |
Workflow Clarity | Check/Fix/Explain/Code Review headers imply a loose sequence but there are no explicit validation checkpoints; the only verification hint ("describe how to confirm the fix in DevTools") is vague, matching the steps-listed-but-validation-gaps anchor. | 2 / 3 |
Progressive Disclosure | The body is a concise overview with a clearly signaled one-level-deep pointer to the real references/rule.md file, matching the clear-overview-with-well-signaled-references anchor. | 3 / 3 |
Total | 8 / 12 Passed |