Database Changes
Overview
Two leaves cover a data schema across its life: first design (keys, constraints, normalisation, idempotency keys) and every later change to a live schema (expand-migrate-contract, batched backfills, safe drops). Design owns the first cut; migrations own every change after go-live.
When to use
- Designing tables, keys, constraints, indexes; choosing relational vs document storage.
- Changing a live schema with no downtime: rename, backfill, drop, type change.
When not to use
- Public API resource or error-shape design — outside this skill.
- Retiring a feature or an API surface wholesale — outside this skill.
- Restoring from backup after data loss — outside this skill.
Precedence
The deepest loaded instruction governs its uniquely-claimed scope; every
scope:string is claimed by exactly one file in this tree; no leaf may widen a prohibition declared by an ancestor — leaves narrow, never override upward.
Subskill index
| Leaf | Task | Trigger |
|---|---|---|
subskills/data-modeling.md |
Schema design | "design the tables" |
subskills/schema-migrations.md |
Zero-downtime schema change | "migrate this column" |
See also
subskills/data-modeling.md— the first design.subskills/schema-migrations.md— every change after go-live.