dbdesign
Installation
SKILL.md
dbdesign
Design the logical model before selecting physical implementation details. When the question is still which stores the system needs — relational or not, how many, what is derived — run dbarchitect first; this skill then designs each relational system of record it names, starting from its load parameters and consistency map. This skill can be used independently for a new design or after dbaudit to redesign an existing database. It proposes a design; it does not apply schema changes or migrations.
Choose the mode
| Mode | Input | Output |
|---|---|---|
| New design | Requirements, domain description, or interview notes | Conceptual model, normalized relational model, and target DDL when the engine is known |
| Audited redesign | Audit report and source schema | Corrected model with each major change traced to audit evidence or a stated requirement |
| Design review | Existing ER model, relational schema, or DDL | Findings and improvement recommendations; rewrite only when requested |
If revising an existing database without an audit, say so. Proceed with the evidence available, mark unknowns, and recommend dbaudit when a defensible assessment is needed. Never claim runtime properties from static DDL.