Enforce the database change protocol and preserve the project's data-modeling philosophy. This skill exists to stop unsafe or off-contract database work.

Non-Negotiables

This project's database workflow is mandatory:

PostgreSQL is the source of truth for persistence behavior.
Goose migrations are the only supported schema-change mechanism.
Migration history must stay aligned with the Goose migration log.
Generated DB types must be regenerated and verified after every schema change.
Destructive or rollout-sensitive changes must be called out explicitly before they ship.

Forbidden behavior:

Do not use another schema or migration framework.
Do not apply schema changes ad hoc through raw psql, GUI clients, or manual DDL outside the migration workflow.
Do not edit a migration that has already been applied to any non-disposable environment.
Do not hand-edit generated type files.
Do not ship application code that depends on a schema change before the migration path is understood and verified.

kernel-database

Non-Negotiables