Content
93%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.
A dense, highly actionable reference focused on non-obvious pitfalls and concrete commands, organized into two clear sections. The only gap is an explicit migration-failure feedback loop, which keeps workflow_clarity at 4 rather than 5.
Suggestions
Add an explicit migration failure feedback loop, e.g. after `check` or `migrate` fails: review the error, fix the schema (not the generated SQL), regenerate, and re-run until `check` passes.
Surface the `drizzle.config.ts` required fields (dialect, schema, out, dbCredentials.url) as a short ordered setup checklist so the 'set up a new Drizzle project' trigger maps to a concrete first-run sequence.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean bullet points with no padding or explanation of concepts Claude already knows (e.g., what an ORM is); every line states a specific, non-obvious gotcha or command. | 5 / 5 |
Actionability | Concrete executable guidance throughout — `drizzle(client, { schema })`, `db.transaction(async (tx) => …)`, `sql.placeholder('id')` + `.prepare('name')`, `ALTER TABLE users RENAME COLUMN old_name TO new_name;`, `postgres(url, { max: 1 })`, and the required `drizzle.config.ts` keys — covering the common cases copy-paste ready. | 5 / 5 |
Workflow Clarity | Clear sequences exist (generate → review SQL → migrate; the two-migration non-nullable-column flow) with checkpoints like '`check` validates migration history consistency' and the destructive column-rename hand-off, but there is no explicit validate → fix → re-validate feedback loop for migration failures. | 4 / 5 |
Progressive Disclosure | Under 50 lines with no external bundle files needed and two well-organized sections ('Gotchas', 'drizzle-kit'); the simple-skill exception applies, so well-organized sections alone warrant the top score. | 5 / 5 |
Total | 19 / 20 Passed |