Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is highly actionable with clear, validated workflows and a clean one-level-deep reference structure. The main weakness is conciseness: several safety rules are restated verbatim across multiple sections and could be consolidated to a single source of truth with brief cross-references.
Suggestions
Consolidate the repeated no-DDL / never-apply-hosted-migrations / @beta rules into one canonical statement and reference it from the other sections instead of restating them each time.
The "CRITICAL: Use the Netlify CLI" and "When something fails, surface and stop" sections overlap on the "never go around the CLI" guidance; merge or cross-link to remove the duplication.
Trim the provisioning section's repeated restatement of the migration-application rule, since it is already covered in the dedicated "CRITICAL: Never apply migrations" section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient and Netlify-specific, but several rules are repeated multiple times (the no-DDL-through-connect rule, the @beta install requirement, and the never-apply-hosted-migrations rule each appear 3+ times across CRITICAL sections, CLI guidance, and Common mistakes), which is verbosity the rubric penalizes even when accurate. | 2 / 3 |
Actionability | It provides fully executable, copy-paste-ready code (schema.ts, drizzle client, drizzle.config.ts, package scripts, query patterns, native driver, transactions) and concrete CLI commands throughout, matching the executable-code anchor. | 3 / 3 |
Workflow Clarity | The preview-first provisioning workflow is an explicitly sequenced numbered list with a validation checkpoint ("Verify the deploy log shows Netlify Database setup completed"), plus a 401 failure playbook, a schema-change workflow with a review step, and a Common mistakes checklist — clear sequences with feedback loops for the database operations the scoring notes flag. | 3 / 3 |
Progressive Disclosure | The body keeps core workflows and critical rules inline while pushing deep detail (full migration workflow, full CLI reference, footguns, legacy coexistence, provider-switch import) into six well-signaled, one-level-deep reference files that all exist under references/, with a described References section at the end. | 3 / 3 |
Total | 11 / 12 Passed |