Content
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is concise and well-structured with sound progressive disclosure, cleanly offloading detail to references/rule.md. It is weaker on actionability and workflow clarity because the body itself lacks executable examples and explicit validation checkpoints.
Suggestions
Add at least one inline, copy-paste-ready snippet (e.g., a minimal jest-axe or AxeBuilder test) so the body is actionable without forcing a file read.
Turn the Check/Fix sections into an explicit sequence with a validation checkpoint — e.g., "run the a11y suite; if violations appear, fix and re-run until <= 0 unexpected violations" — to add a validate-fix-retry loop.
Surface one concrete CI invocation command (e.g., `npm run test:a11y`) directly in the body so the CI/CD guidance is executable rather than descriptive.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean — a short framing line, a Quick Reference bullet list, and terse Check/Fix/Explain/Code Review sections — with no padding or explanation of concepts Claude already knows; not a 2 because there is no unnecessary explanation to tighten. | 3 / 3 |
Actionability | Names concrete tools (jest-axe, @axe-core/playwright, cypress-axe) and specific rules ("color-contrast"), but the body contains no executable code or commands and several sections (Check/Fix/Explain) are directive verbs that describe rather than instruct with copy-paste-ready specifics; not a 3 because nothing in the body is copy-paste ready, and not a 1 because specific tool names and rule targets give real guidance. | 2 / 3 |
Workflow Clarity | The Check/Fix/Explain/Code Review sections imply a loose sequence but there are no explicit validation checkpoints or a validate-fix-retry feedback loop in the body; not a 3 because checkpoints are absent rather than merely implicit, and not a 1 because a recognizable sequence of stages is present. | 2 / 3 |
Progressive Disclosure | The body is a clear overview that explicitly signals a one-level-deep reference ("see references/rule.md"), and the referenced file genuinely holds the detailed content; not a 2 because the reference is clearly signaled and shallow rather than nested or poorly organized. | 3 / 3 |
Total | 10 / 12 Passed |