Content
71%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, mostly lean backend playbook with a clear sequenced workflow, validation checkpoints, and concrete numbered rules. Its main weaknesses are minor architectural-pattern redundancy and progressive-disclosure references that point to bundle files which are not actually present.
Suggestions
Ship the referenced bundle files (resources/execution-protocol.md, resources/checklist.md, resources/orm-reference.md, resources/error-playbook.md, and the ../_shared/core/* set) so the clearly-signaled references resolve to real content.
Consolidate the layered-architecture explanation so the Router→Service→Repository→Models pattern is stated once and the per-layer sections only add layer-specific rules, removing the restatement in Core Rule #1.
Add one or two copy-paste code snippets for the most common backend cases (e.g. a parameterized query and a service-scoped transaction unit-of-work) to push actionability toward fully executable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is directive and assumes Claude's competence — rules and standards rather than tutorials — with no concept-explanation padding. It loses a point because the Router→Service→Repository→Models pattern is stated in the Architecture Pattern, restated across three layer sections, and again in Core Rule #1. Efficient with minor instances of over-explanation that could be trimmed; not 5 due to that redundancy, not 3 because it is not noticeably padded. | 4 / 5 |
Actionability | Provides concrete executable guidance: an action→SSL-primitive table, a canonical `rg` workflow, an architecture diagram, and 13 numbered rules with specifics (e.g. 'JWT + Argon2id', 'parameterized queries only', the env-fallback pattern with a `// TODO(oma-deferred)` marker). Mostly executable; not 5 because code examples are thin (only two `rg` lines) with no copy-paste snippet for common cases, not 3 because the guidance is concrete rather than pseudocode. | 4 / 5 |
Workflow Clarity | Clear sequencing via Entry steps, the PREPARE→ACQUIRE→ACT→VERIFY→FINALIZE scenes, explicit failure/recovery, and a VERIFY checkpoint with 'fix root cause before handoff' plus a referenced checklist — a feedback loop for migration/persistence work. Not 5 because the checklist/feedback loop is referenced rather than inline and lightly specified; not 3 because validation checkpoints are explicitly present, satisfying the destructive/batch cap. | 4 / 5 |
Progressive Disclosure | The body is well-sectioned with a clear one-level-deep References list pointing to resources/*.md and ../_shared/core/*.md files. However the referenced bundle files do not exist in the bundle (references/, scripts/, assets/, resources/, ../_shared are all absent), so the signaled navigation leads nowhere. Not 4 because the referenced targets are missing and navigation is undermined; not 2 because structure and signaling are genuinely present and bulk is appropriately deferred to references. | 3 / 5 |
Total | 15 / 20 Passed |