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-organized, token-efficient overview with excellent progressive disclosure to a real, one-level reference file. Its main weakness is actionability: the Check/Fix sections name the error types but never give an executable validation command or a concrete way to inspect rendered output, leaving the how-to entirely to the reference.
Suggestions
Name a concrete validation tool in the Check section (e.g., W3C validator, `npx html-validate .`, or `tidy -errors index.html`) so the check is executable without opening the reference.
Add a one-line re-validation step after Fix (re-run the validator against the rendered output) to close the feedback loop within the body.
Merge the overlapping Quick Reference, Check, and Fix sections into a single streamlined section to remove the triplicated guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean, assumes Claude's competence (no explanation of what HTML is), and every section is brief. Not 5 because of minor redundancy: the "Quick Reference" bullets largely restate "Check" and "Fix", and the thin "Explain" section adds little. Not 3 because there is no unnecessary explanation or padding beyond that overlap. | 4 / 5 |
Actionability | Concrete error types are named ("unclosed tags, incorrect nesting, or structural errors", "stray tags or unescaped characters") but no executable tool or command is given — no validator (W3C validator, html-validate, tidy) and no concrete step for inspecting rendered output (e.g., curl or devtools); code examples live only in the reference file. Not 4 because the body lacks a specific executable step; not 2 because the guidance specifies what to look for rather than offering only high-level hints. | 3 / 5 |
Workflow Clarity | A clear Check → Fix → Explain → Code Review sequence is present, and the referenced rule.md adds a Verification section (automated and manual checks, re-crawl after deployment). Not 5 because the body itself has no explicit re-validate-after-fix checkpoint; the validation loop only appears in the reference. Not 3 because the sequence and checkpoints are mostly explicit and this is not a destructive/batch operation. | 4 / 5 |
Progressive Disclosure | The body is a concise, well-sectioned overview (under 50 lines) that delegates implementation details to a single one-level-deep reference, `references/rule.md` (verified to exist, no further nesting), clearly signaled with what it contains ("full implementation details, code examples, and framework-specific guidance"). Matches the top anchor: clear overview, well-signaled one-level reference, easy navigation. | 5 / 5 |
Total | 16 / 20 Passed |