Content
63%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 well structured with an excellent progressive-disclosure split — a lean overview correctly pushing code and framework guidance to the existing one-level-deep rule.md. Its weaknesses are redundancy (the SOP explainer and Check/Fix/Explain/Code Review prose restate the Quick Reference bullets) and the absence of any concrete code or commands in the body itself, leaving the Check/Fix guidance at the prose level.
Suggestions
Drop or compress the Same-Origin Policy intro paragraph — Claude already knows SOP/CORS basics — and let the reference's 'Why It Matters' section carry that context.
Collapse the overlapping Check/Fix/Explain/Code Review prose into the Quick Reference bullets plus one review-workflow step list, eliminating the near-verbatim repetition of the description.
Inline one tiny good/bad snippet (e.g. the ALLOWED_ORIGINS postMessage guard) so the most common fix is executable directly from the body without opening the reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body opens by explaining the Same-Origin Policy — 'The Same-Origin Policy is the browser's primary defense against malicious sites stealing data' — which is knowledge Claude already has, and the Check/Fix/Explain/Code Review prose sections substantially restate the Quick Reference bullets and each other (e.g. 'Review scripts, client components, and browser execution paths' repeats the description nearly verbatim). Mostly efficient, but it could be tightened to the bullet list plus the reference pointer. | 3 / 5 |
Actionability | The Quick Reference bullets name exact, checkable patterns ('verify event.origin before processing postMessage data', 'Never set Access-Control-Allow-Origin: * for authenticated endpoints', 'Reject unvalidated redirect targets such as `next`, `redirect`, or `callbackUrl`'), but the body itself contains no code or commands — all executable examples are deferred to references/rule.md, and the Check/Fix sections are prose descriptions ('Add origin validation to postMessage listeners and review CORS configuration') rather than concrete steps. | 3 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sections form a clear, coherent review sequence, and the Code Review section explicitly requires stating 'how the change should be verified in the browser', with detailed verification steps one level deep in rule.md. Not a 5 because the validation loop (verify → fix → re-verify) is referenced rather than laid out as explicit checkpoints in the body. | 4 / 5 |
Progressive Disclosure | A ~35-line, well-sectioned overview that defers all implementation detail via a clearly signaled, one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`' — and that file exists and appropriately carries the code examples and verification steps. Structure and split match the top anchor. | 5 / 5 |
Total | 15 / 20 Passed |