Content
57%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 well structured with exemplary progressive disclosure — a lean overview correctly deferring detail to a single clearly-signaled reference file. It is dragged down by verbatim duplication of the harm statement across three sections, absence of any detection/verification detail in the body itself, and no explicit verification checkpoint in the Check/Fix workflow.
Suggestions
Delete the Explain section (or the intro paragraph) — the sentence "Scrolljacking breaks user expectations, interferes with assistive technologies, and creates unpredictable experiences..." is repeated verbatim in both, and near-verbatim in the Quick Reference bullet.
Move at least one concrete detection method from references/rule.md into the Check section (e.g., the console wheel-event defaultPrevented test) so the body's guidance is executable without opening the reference.
Add an explicit verification step to the Check/Fix flow (e.g., "Verify: scroll with mouse wheel and keyboard Page Up/Down; confirm movement feels native and all content including the footer is reachable") rather than only instructing to "note how to verify the fix".
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The harm statement "Scrolljacking breaks user expectations, interferes with assistive technologies, and creates unpredictable experiences..." appears verbatim in both the intro and the Explain section, and near-verbatim again as a Quick Reference bullet — the entire Explain section restates the intro and could be cut. It is not a 2 because the body is brief overall with no explanation of concepts Claude already knows. | 3 / 5 |
Actionability | The Fix section gives concrete direction ("Remove JavaScript that overrides default scroll behavior... respect prefers-reduced-motion") and Check names specific things to inspect, but the body contains no method, command, or detection snippet for how to test or verify — all executable detail is deferred to the reference. This is incomplete concrete guidance rather than the minor gaps of a 4. | 3 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sections imply a recognizable sequence, but no verification checkpoint exists in the body; Code Review only says to "note how to verify the fix with browser accessibility tooling" without an actual verification step (manual checks live only in the reference). Sequence present with implicit/missing checkpoints matches the anchor. | 3 / 5 |
Progressive Disclosure | The body is a concise, well-sectioned overview under 50 lines that cleanly splits implementation detail, code examples, and framework guidance into references/rule.md — a real file, one level deep, clearly signaled with an explicit "For full implementation details... see references/rule.md" pointer. This matches the clear-overview, well-signaled one-level-deep reference pattern. | 5 / 5 |
Total | 14 / 20 Passed |