Content
78%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.
The body is a well-structured, token-efficient overview that assumes competence, delegates code to a real one-level-deep reference, and provides specific, actionable instruction via named APIs. The main gaps are mild redundancy between Quick Reference and the Check/Fix sections and the absence of any minimal inline example.
Suggestions
Collapse the duplicate native-vs-custom guidance: keep it once (e.g., in Check, where the decision is made) and drop the restated advice in Quick Reference and Fix to save tokens.
Add a 5–10 line minimal constructor snippet in the body (attachInternals + ariaRole + formAssociated) so the core fix is executable without opening references/rule.md, and let the reference carry the full component.
Merge or cross-link the Fix and Code Review sections, which currently restate the same checklist (internals attachment, ARIA reflection, keyboard handling, form association) from two angles.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~47-line body is lean and delegates implementation to references/rule.md, but there is mild redundancy: the native-control-first advice appears in both Quick Reference ("Prefer native <button>...") and Fix ("Replace the component with native HTML"), and form association is restated across Quick Reference, Fix, and Code Review. This matches 'efficient; minor instances of over-explanation that could be trimmed' rather than the lean 5. | 4 / 5 |
Actionability | Guidance names exact APIs — "ElementInternals.ariaRole", "attachInternals" in the constructor, "formAssociated", roving tabindex, and the specific keys (Tab, Enter, Space, Arrow) — which is actionable, specific instruction. However, no inline code snippet exists (all code lives one level deeper in references/rule.md), leaving minor gaps versus fully copy-paste-ready guidance. | 4 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sections give a clear implicit sequence for a review task (verify native alternative first, then check, then fix, then explain). This is effectively a single-purpose review skill with an unambiguous action, but the sequence is conveyed by section roles rather than explicit steps or checkpoints — solidly between the simple-skill 5 and the checkpointed 4. | 4 / 5 |
Progressive Disclosure | The body is under 50 lines with well-organized sections (Quick Reference, Check, Fix, Explain, Code Review) and a single clearly signaled, one-level-deep reference to references/rule.md, which exists and carries the full implementation details and code. This matches the anchor of a clear overview with a well-signaled one-level reference and easy navigation. | 5 / 5 |
Total | 17 / 20 Passed |