Database Schema Specs Before Migrations
Define database schemas before writing migrations, including columns, constraints, indexes, API alignment, and rollout order.
Paginated browsing for the full Spec Coding article archive. These pages keep long lists readable while preserving direct links.
Define database schemas before writing migrations, including columns, constraints, indexes, API alignment, and rollout order.
AI coding tools drift without constraints, adding fields, renaming functions, expanding scope, and inventing tests. Spec-first prompts keep changes reviewable.
Govern AI-assisted coding with spec-driven prompts: define scope, boundaries, evidence, and audit trails before generated code reaches review.
Review AI-generated pull requests against acceptance criteria: inspect the diff, run evidence checks, and catch failures a quick skim misses.
Use a pre-merge risk register for AI-generated code: flag auth, data, contract, migration, rollback, and observability risks.
Use test-evidence gates for AI-generated code: require meaningful tests before merge and catch hallucinated implementations before release.
Design API specs for LLM-powered agentic clients with discoverable fields, idempotency, dry-runs, semantic descriptions, and safe destructive actions.
Add contract testing from OpenAPI to CI with generated tests, provider checks, consumer expectations, and reliable fixtures.
Specification patterns for event-driven systems: schema versioning, command vs fact events, orchestration choices, idempotent handlers, and replay safety.
Write payment workflow specs with retryable errors, declined-card handling, timeout behavior, 3DS branches, and dunning states.
Avoid ten specification mistakes that hide decisions, blur acceptance criteria, skip failure paths, and push scope arguments into implementation.
Quality gates for AI-assisted code: pre-prompt spec checks, diff review, test evidence, and human sign-off before generated code ships.
Static pagination page · 2/3