Content
65%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A lean, well-structured overview that uses progressive disclosure correctly by deferring code and verification detail to a single clearly-signaled reference file. The body itself is directive rather than executable, and the workflow lacks an explicit post-fix validation checkpoint.
Suggestions
Inline one small executable snippet in the Fix section (e.g., a two-line scroll-padding-top/bottom CSS rule) so the most common remediation is actionable without opening the reference file.
Add an explicit validation step after Fix, such as 'Re-tab through the page with all sticky UI active and at 200% zoom; pass only if the focused element and its indicator stay visible' — the pass/fail criteria currently live only in references/rule.md.
Trim the introductory rationale sentence ('Keyboard users need to see the actual focused control... to continue the task') to a single clause, since it explains a concept Claude already knows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~35-line body is efficient with well-scoped Check/Fix/Explain/Code Review sections, but the intro sentence explaining that keyboard users 'need to see the actual focused control and the focus indicator at the same time in order to continue the task' briefly restates a concept Claude already knows. Matches the 4 anchor (efficient, minor trimmable instances) rather than the lean 5 anchor. | 4 / 5 |
Actionability | Directives name concrete targets ('headers, footers, cookie banners, promo bars, and chat launchers') and techniques ('scroll-padding', 'reduce overlay height'), but the body contains no executable code, commands, or selectors — all implementation detail is deferred to references/rule.md. This sits between the vague-hints of 2 and the mostly-executable guidance of 4. | 3 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sections imply a coherent sequence, but there is no explicit validation checkpoint (e.g., re-test tabbing after applying the fix); pass/fail criteria exist only in the reference file. This matches the 3 anchor (sequence present, checkpoints missing or implicit) rather than 4. | 3 / 5 |
Progressive Disclosure | The body is a concise, well-sectioned overview that clearly signals a single one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), which is a real, self-contained file with no nested references. This matches the 5 anchor exactly. | 5 / 5 |
Total | 15 / 20 Passed |