Content
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is a well-structured overview with good progressive disclosure to a real reference file, but its workflow steps lack explicit verification checkpoints and its guidance is only partially actionable, with some redundant meta-explanation. Tightening the Check/Fix steps and adding a concrete verification step would lift the weaker dimensions.
Suggestions
Replace the vague "Search for any role attributes..." Check step with a concrete method, e.g. a CSS/attribute selector like `[role]` or an axe/Lighthouse check command, so guidance is copy-paste ready.
Add an explicit verification checkpoint to the workflow (e.g. "Confirm the fix in the browser accessibility tree or with a screen reader before closing the review") rather than only implying it.
Trim or repurpose the "Explain" section so it does not instruct Claude to explain why standardized ARIA matters — a concept it already knows — and keep only reviewer-facing guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean, but the "Explain" section directs Claude to explain why standardized ARIA roles are critical — a concept Claude already knows — and the "Code Review" section partly restates guidance, keeping it just above the fully-lean anchor. | 2 / 3 |
Actionability | The Quick Reference gives concrete examples (use "checkbox" not "check-box"; prefer native <button>/<input>/<select>) but the "Check" step is vague ("Search for any role attributes...") with no specific selector, command, or tool, matching the incomplete-guidance anchor. | 2 / 3 |
Workflow Clarity | Sequenced Check → Fix → Explain → Code Review sections are present, but verification is only weakly implied ("note how to verify the fix") with no explicit validation checkpoint in the body itself, fitting the "sequence present but checkpoints missing" anchor. | 2 / 3 |
Progressive Disclosure | The body is a concise overview that clearly signals a single one-level-deep reference ("see references/rule.md"), and references/rule.md exists with the detailed code, rationale, exceptions, and verification — matching the well-signaled one-level reference anchor. | 3 / 3 |
Total | 9 / 12 Passed |