Content
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body has a clear, well-validated workflow and some genuinely actionable directives, but it is padded with redundant stack listings and abstract process frameworking, and its progressive disclosure is undermined by a duplicated, partly-broken reference layout with no backing bundle files.
Suggestions
De-duplicate the stack: keep one authoritative Libraries table and remove the repeated React/Next.js/TypeScript/Tailwind/shadcn entries from Dependencies and Tools and instruments.
Collapse the abstract SSL-primitive action table and PREPARE/ACQUIRE/ACT scenes into the concrete Entry→VERIFY→Exit flow, or move them to a referenced resource so the body stays lean.
Consolidate the References section into a single, clearly signaled list and ensure each referenced resources/*.md file actually exists in the bundle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The stack is restated three times (Dependencies, the Libraries table, and Tools and instruments) and the References section lists resources twice in different formats; the abstract SSL-primitive and PREPARE/ACQUIRE/ACT scenes framing adds overhead Claude does not need. | 2 / 3 |
Actionability | Concrete bits exist (rg discovery commands, a versioned/banned Libraries table, named shadcn registry tools, explicit guardrails like 'treat components/ui/* as read-only'), but actual executable code examples are deferred to resources/examples.md and the Structural Flow is described abstractly rather than instructed. | 2 / 3 |
Workflow Clarity | A clear Entry → Scenes (PREPARE/ACQUIRE/ACT/VERIFY/FINALIZE) → Transitions → Failure and recovery → Exit sequence is given, with an explicit VERIFY checkpoint, a referenced checklist, and a feedback loop ('If verification fails, fix before handoff or report the blocker'). | 3 / 3 |
Progressive Disclosure | References are one level deep and signaled, but no bundle files actually exist in references/scripts/assets, the reference list is duplicated and inconsistently formatted (numbered list then a separate bullet list), and the body itself is a ~195-line monolithic wall rather than a lean overview pointing outward. | 2 / 3 |
Total | 9 / 12 Passed |