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, appropriately scoped overview that delegates code and verification detail to a real, clearly-labeled reference file. Its main weakness is redundancy — Quick Reference, Check, and Fix restate the same three facts, and the Explain and Code Review sections add templated direction rather than new value.
Suggestions
Consolidate the overlapping Quick Reference, Check, and Fix sections into one section — prefers-reduced-motion, the 3-flashes/second limit, and motion warnings are each stated two to three times.
Trim the Explain section's direction to explain concepts Claude already knows (vestibular disorders, why motion controls matter) down to a single line or fold it into Check.
Inline a minimal @media (prefers-reduced-motion: reduce) snippet in the Fix section so the core remedy is visible without opening the reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and on-topic, but the same facts are repeated across sections — prefers-reduced-motion, the 3-flashes/second limit, and motion warnings each appear in Quick Reference, Check, and Fix — and the Explain section directs Claude to explain concepts it already knows ("Explain how motion affects users with vestibular disorders..."). Mostly efficient but could be meaningfully tightened, fitting anchor 3 rather than 4. | 3 / 5 |
Actionability | The guidance is concrete and executable: a named mechanism ("Use @media (prefers-reduced-motion: reduce) to disable animations"), a measurable threshold ("Never flash content more than 3 times per second"), and specific substitution strategies ("Replace motion with opacity/color transitions"), with complete code one clearly-signaled hop away in references/rule.md. Minor gaps — no inline snippet and soft directives like "Provide motion warnings for immersive experiences" — keep it below anchor 5. | 4 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sections give a coherent review sequence, and verification is addressed ("note how to verify the fix with browser accessibility tooling" plus the Verification section in rule.md). It falls short of anchor 5 because steps are prose paragraphs rather than explicit checkpoints, and validation guidance lives mostly in the reference file instead of being an inline step. | 4 / 5 |
Progressive Disclosure | The ~45-line body is well-sectioned and defers all implementation detail to a single one-level-deep reference that exists in the bundle and is clearly signaled with its contents described ("For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — verified present). This matches anchor 5: clear overview, well-signaled shallow reference, easy navigation. | 5 / 5 |
Total | 16 / 20 Passed |