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, well-organized, and uses progressive disclosure cleanly by deferring code and verification detail to a single real reference file. The main gap is that actionable verification and a copy-paste-ready example are absent from the body itself, weakening actionability and the validation feedback loop.
Suggestions
Surface at least one minimal copy-paste-ready code snippet in the body (e.g. a labeled <nav aria-label=...> example) so the guidance is executable without opening the reference.
Add an explicit in-body validation step such as 'Verify each nav region has a unique aria-label/aria-labelledby and check for div-based or nested nav' to close the verify-fix-retry loop.
Tighten the Check/Fix/Explain sections, which repeat overlapping guidance, into a single concise review checklist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and well-sectioned, assumes Claude's competence, and avoids explaining what HTML, nav elements, or screen readers are, with every section earning its place. | 3 / 3 |
Actionability | Guidance is concrete (named elements, specific aria-label strings like 'Main navigation'), but the body holds no executable example and the Check/Fix/Explain guidance is partly repetitive rather than fully copy-paste ready. | 2 / 3 |
Workflow Clarity | A review sequence (Check/Fix/Explain/Code Review) is present, but explicit validation checkpoints live only in the bundled rule.md rather than the body, so the verify-fix-retry loop is implicit. | 2 / 3 |
Progressive Disclosure | The body is a concise overview that points exactly one level deep to a single real reference file (references/rule.md, confirmed to exist), with a clearly signaled pointer and no nested references. | 3 / 3 |
Total | 10 / 12 Passed |