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 clean, brief overview that delegates implementation detail appropriately to references/rule.md. Its weaknesses are duplicated guidance between the Quick Reference, Check, and Fix sections, the absence of any inline executable example or concrete measurement step, and a workflow that lacks an explicit verify-after-fix checkpoint.
Suggestions
Inline one minimal executable snippet (e.g. the blocking vs async/defer head comparison from the reference) so the fix is copy-paste ready without opening the reference file.
Make the Check step concrete: specify what to look for in Chrome DevTools' Network waterfall (third-party requests on the critical path, script request start time vs main-thread blocking) or a Lighthouse audit to run.
Add an explicit post-fix verification checkpoint (re-run Lighthouse / re-check the waterfall and compare before/after) so the workflow closes the loop, and merge the redundant Check/Fix lines into the Quick Reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with well-chosen bullets, but the Check and Fix lines largely restate the Quick Reference bullets, and the "#1 cause of slow websites ... 2-5 seconds" motivation line is padding Claude does not need — minor trim potential, not full token efficiency. | 4 / 5 |
Actionability | The Quick Reference gives concrete directives ("Use async for independent scripts (analytics, ads)", "Use defer for DOM-dependent scripts"), but the body contains no executable code, no specific DevTools/Lighthouse procedure in the Check section, and the Code Review section is abstract ("Flag exact files, requests, or rendering steps"), with all executable detail deferred to the reference file. | 3 / 5 |
Workflow Clarity | A rough Check → Fix → Explain sequence exists via section ordering, but checkpoints are implicit: the Check step is vague ("Analyze third-party scripts on this page to ensure they use async/defer") and there is no post-fix re-measure step to confirm the change improved load time. | 3 / 5 |
Progressive Disclosure | A short, well-sectioned body with a clearly signaled, one-level-deep pointer ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`"); the reference file exists and carries the code examples, with no nested references. | 5 / 5 |
Total | 15 / 20 Passed |