04-database-design
Installation
SKILL.md
Database Design Skill
Use When
- Persistent data structures must be specified before implementation or migration.
Do Not Use When
- Do not use to design API payloads, bypass domain ownership, or optimise from guessed queries.
Required Inputs
| Artefact | Source or provider | Required? | Missing behaviour |
|---|---|---|---|
| Approved entity rules and access patterns | SRS, HLD and API contracts | Required | Stop if ownership, lifecycle or identifiers are unresolved. |
| Workload, tenancy, retention and migration constraints | Operations, security and data owners | Required | Qualify absent volume evidence and avoid speculative indexes. |