Content
65%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, token-efficient overview that uses progressive disclosure effectively by deferring detailed code to a one-level-deep reference. It is weakest on in-body actionability and workflow feedback, since the executable steps and a re-measure loop live only in the reference.
Suggestions
Add one concrete measurement snippet in the Check section (e.g., the web-vitals onINP call or the exact DevTools panel/path) so the body is executable without opening the reference.
Add an explicit re-measure feedback loop (measure → apply fix → re-measure to confirm INP < 200ms) to close the optimization workflow.
De-duplicate the intro and the Explain section, which restate the same INP definition, to recover tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean, assumes Claude's competence, and defers all code to the reference; the only redundancy is that the intro and the "Explain" section restate the same INP definition, which keeps it just below anchor 5. | 4 / 5 |
Actionability | Provides some concrete pointers (named tools DevTools/PageSpeed Insights and a 200ms threshold) but no executable code or specific steps in the body itself; the "Fix" section lists techniques (break up long tasks, web workers) without implementation, leaving guidance incomplete. | 3 / 5 |
Workflow Clarity | A clear Check → Fix → Explain → Code Review sequence exists with an initial 200ms validation checkpoint, but there is no re-measure/verify feedback loop after applying fixes, so checkpoints are incomplete. | 3 / 5 |
Progressive Disclosure | A concise, well-sectioned overview points to a single clearly signaled one-level-deep reference (references/rule.md, verified to exist) that holds the code examples and tables, splitting content appropriately with easy navigation. | 5 / 5 |
Total | 15 / 20 Passed |