Content
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is well-structured with a clean Quick Reference and a properly signaled one-level reference, but it carries some explanatory padding Claude doesn't need and keeps its executable code and verification steps in the reference rather than inline.
Suggestions
Trim or remove the opening paragraph explaining keyboard users and WCAG rationale; Claude already knows this, and it duplicates rule.md's "Why It Matters".
Add a minimal inline CSS snippet (a before/after outline:none → :focus-visible pair) so the body is self-sufficient for the common case without requiring a file hop.
Add an explicit verify step to the Check or Code Review section (e.g. confirm the computed :focus-visible style is visible in DevTools) so the workflow has a validation checkpoint in the body itself.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient (tight Quick Reference bullets), but the opening paragraph explains who keyboard users are and why focus matters — concepts Claude already knows — and largely duplicates rule.md's "Why It Matters" section. | 2 / 3 |
Actionability | The Quick Reference gives concrete, specific guidance (3:1 contrast, 2px outline, prefer :focus-visible), but no executable CSS code block lives in the body — copy-paste examples are delegated to references/rule.md. | 2 / 3 |
Workflow Clarity | Check, Fix, and Code Review sections imply a loose find-then-flag sequence, but there is no explicit validation/verification checkpoint in the body; the verification steps live only in the reference file. | 2 / 3 |
Progressive Disclosure | The body is a well-organized overview that clearly signals a single one-level-deep reference ("see `references/rule.md`"), which exists as a real file, splitting detail appropriately. | 3 / 3 |
Total | 9 / 12 Passed |