Content
61%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 dense, actionable reference with strong executable examples and good offloading of the deepest detail to a real reference file. It loses points for inlining standard patterns Claude already knows and for being a pattern catalog without consistent validated workflows.
Suggestions
Move standard, well-known patterns (basic CRUD endpoint list, Zod basics, JWT login/refresh/logout flow) into a reference file or trim them, keeping only the non-obvious team conventions inline to improve conciseness.
Add explicit validation checkpoints to the core operations — e.g., a validate-fix-retry loop for schema/migration changes and a verification step after creating endpoints — to raise workflow clarity above the pattern-catalog baseline.
Close the minor executable gaps in the code samples (define or import `verifyAccessToken`, type the Express middleware args, avoid `model: any`) so examples are fully copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and rich with non-obvious team decisions (per-endpoint rate limiting, jitter, circuit-breaker states, idempotency), but ~670 lines inline several standard patterns Claude already knows (basic CRUD, Zod basics, JWT flow) that could be tightened. | 3 / 5 |
Actionability | Largely executable copy-paste code across Prisma, Zod, middleware, retry, circuit breaker, and better-sqlite3 patterns, with minor gaps such as the undefined `verifyAccessToken`, `model: any`, and untyped req/res/next signatures. | 4 / 5 |
Workflow Clarity | A pattern catalog rather than a unified workflow: the zero-downtime migration checklist and auth flow are well-sequenced with rollback/staging checkpoints, but most operations (endpoint creation, schema changes) lack explicit validate-then-fix-retry feedback loops. | 3 / 5 |
Progressive Disclosure | Well-sectioned with clearly signaled one-level-deep references to the existing `references/idempotencia-e-postgres-avancado.md` (cited twice), but substantial code and detail remain inlined in the body that could live in reference files. | 4 / 5 |
Total | 14 / 20 Passed |