Content
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, lean overview that delegates implementation detail to a clearly signaled one-level-deep reference. Its weaknesses are the lack of executable code and explicit validation checkpoints in the body itself, plus a slightly conceptual intro paragraph.
Suggestions
Move or tighten the introductory word-order explanation so the body leads with actionable rules rather than a concept Claude already knows.
Add one minimal executable code snippet in the body (e.g. a named-placeholder t() call) so guidance is concrete before deferring to references/rule.md.
Surface at least one verification checkpoint in the body (e.g. grep for t('key') + concatenation) rather than leaving all validation steps in the reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean with single-sentence sections and tight Quick Reference bullets, but the intro paragraph explains word-order variation across languages — a concept Claude already knows — and could be trimmed; not a 1 because most of the body is efficient, not a 3 because of the conceptual preamble. | 2 / 3 |
Actionability | Names concrete techniques ("named placeholders", "ICU MessageFormat", "pluralisation handled via the library") but provides no executable code in the body — all examples are deferred to references/rule.md; not a 1 because the guidance is specific, not a 3 because nothing in the body is copy-paste ready. | 2 / 3 |
Workflow Clarity | Sections (Check, Fix, Explain, Code Review) imply a review→fix→explain sequence but lack explicit ordering or validation checkpoints, and the verification steps live only in the reference file; not a 1 because structure is present, not a 3 because checkpoints are implicit and validation is externalized. | 2 / 3 |
Progressive Disclosure | The body is a concise overview that clearly signals a single one-level-deep reference ("see references/rule.md", which exists) for full implementation details; not a 2 because navigation is explicit and content is appropriately split. | 3 / 3 |
Total | 9 / 12 Passed |