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 an efficient, well-organized catalog of 70 rules with concrete API-level one-liners, but it functions purely as an index: all executable detail is deferred to rule files that are not present in the bundle, and there is no explicit workflow for applying the rules. It needs either inlined key examples or shipped, verified reference files to be fully usable.
Suggestions
Inline one or two short code examples for the highest-priority rules (e.g., async-parallel, bundle-barrel-imports) so the quick reference is actionable even without the rule files.
Add an explicit application workflow, e.g., 'When reviewing code: 1) match the task to a category by priority, 2) locate the rule by prefix, 3) read rules/<prefix>-<name>.md before refactoring.'
Ship the referenced bundle files (rules/*.md and AGENTS.md) or fix the references — the body's core navigation ('Read individual rule files', 'For the complete guide with all rules expanded: AGENTS.md') currently points at files that do not exist in the bundle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a lean index — 70 one-line rule summaries like "Use Promise.all() for independent operations" with no explanations of concepts Claude already knows. Minor duplication (the priority table repeats category/impact/prefix info already shown in section headers, and 'When to Apply' restates the frontmatter description) keeps it just below anchor 5's "every token earns its place". | 4 / 5 |
Actionability | One-liners name concrete APIs ("Use React.cache() for per-request deduplication", "Use next/dynamic for heavy components"), but many rules are too terse to apply ("Use better-all for partial dependencies") and all code examples are deferred to rules/*.md files. This matches anchor 3 ("Some concrete guidance but incomplete... missing key details") rather than anchor 4's "mostly executable guidance". | 3 / 5 |
Workflow Clarity | The navigation flow (priority table → category quick reference → rule file) is implied but never given as an explicit sequence; "How to Use" only says "Read individual rule files for detailed explanations" with no steps for applying rules during writing vs. reviewing vs. refactoring. Anchor 3 fits: structure present but the usage sequence remains implicit. | 3 / 5 |
Progressive Disclosure | The body is structured as an index with clearly signaled one-level-deep references ("rules/async-parallel.md", "AGENTS.md"), but none of the referenced files exist in the provided bundle — there is no rules/ directory, references/, or AGENTS.md, so the disclosure chain dead-ends. Good signaling and structure, but unverifiable/broken references keep it at anchor 3 rather than anchor 4. | 3 / 5 |
Total | 13 / 20 Passed |