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 excellent progressive disclosure — a lean overview delegating code examples and framework specifics to a single, real, one-level-deep reference file. Its weaknesses are padding from known-concept explanations, duplicated review instructions across the Check and Code Review sections, and a Fix section that gives high-level direction without any inline executable guidance or concrete verification steps.
Suggestions
Cut the known-concept explanations — the opening motivation line and the debounce/throttle definitions in Quick Reference — and keep only the non-obvious specifics (the 150-300ms/100ms timing values and the listener-cleanup reminder).
Merge the redundant 'Check' and 'Code Review' sections into a single review section; both currently repeat near-identical instructions to review code for high-frequency event handlers.
Add one minimal inline debounce or throttle implementation (or surface a snippet from references/rule.md) in the Fix section, and turn 'state how the change should be verified in the browser' into a concrete verification step such as checking handler invocation frequency in the DevTools Performance panel.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short but spends tokens on concepts Claude already knows — 'Debounce: delays execution until activity stops (search inputs, form validation)' and the opening motivation line about UI jank and INP — and the 'Check' and 'Code Review' sections repeat near-identical review instructions, so it could be tightened rather than being fully lean. | 3 / 5 |
Actionability | There is some concrete guidance ('Use 150-300ms delay for user input, 100ms for scroll/resize', the scroll/resize/input/mousemove event list, 'Flag exact imports, event handlers, runtime side effects') but no executable code in the body — the Fix section says only 'Add debounce or throttle to high-frequency event handlers' and defers all implementation to references/rule.md, leaving key details one hop away. | 3 / 5 |
Workflow Clarity | A rough Check → Fix → Explain sequence is present, but checkpoints are only implicit: 'state how the change should be verified in the browser' directs Claude to describe verification rather than providing an actual validation step, and the redundant Check/Code Review sections blur the sequence. | 3 / 5 |
Progressive Disclosure | The body is a well-organized ~35-line overview that clearly signals one level of external depth ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), and references/rule.md exists, is self-contained (no nested references), and appropriately holds the code examples and framework guidance — matching the clear-overview anchor. | 5 / 5 |
Total | 14 / 20 Passed |