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.
A lean, well-structured instructional body with concrete thresholds and a clean hand-off to a single reference file. The main issue is redundancy: the Explain section and the Check/Code Review pair repeat content that could be consolidated, which is the main token-efficiency cost.
Suggestions
Merge the "Check" and "Code Review" sections, which both describe counting same-domain <a href> links in <main>/<article> and excluding templated navigation — keep one authoritative procedure.
Drop or fold the "Explain" section: it restates the intro's crawler-discovery concept that Claude already knows; at most keep the one non-obvious point about edges in the link graph.
Add a brief note on handling intentional exceptions (login, utility, staging pages) or point to the Exceptions section of references/rule.md so flagged pages aren't treated as fixable dead ends.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The "Explain" section ("Internal links are the edges of your site's graph. Crawlers navigate by following links...") re-explains the crawler concept already stated in the intro, and "Check" and "Code Review" give near-duplicate counting/exclusion instructions. Not a 2 because each section is individually brief, but the redundancy is more than minor. | 3 / 5 |
Actionability | Concrete, executable guidance: parse "<main> or <article>", count same-domain "<a href>" links, flag pages with "fewer than 2", add "2–5 topically related pages" with a worked CSS Grid example and a fallback "Related articles" section. Minor gap: no actual crawler command or script invocation inline (deferred to the reference). | 4 / 5 |
Workflow Clarity | The Fix section is a clear six-step sequence with a verification checkpoint ("Re-crawl after changes to verify the links appear in the rendered DOM"). Not 5 because there is no error-recovery loop for flagged pages that are intentional exceptions (e.g. login or utility pages), which the reference file covers but the body omits. | 4 / 5 |
Progressive Disclosure | A short, well-sectioned overview (Quick Reference, Check, Fix, Explain, Code Review) with a clearly signaled one-level-deep pointer: "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — the file exists and contains exactly that. | 5 / 5 |
Total | 16 / 20 Passed |