dbdesign

# DB Design Design database schemas from requirements, existing data, and query patterns. This skill covers modeling decisions and review quality; use `vd:miudb` or the `sqlit` CLI to inspect live databases, `vd:diagram` for ERDs, and `vd:cnpg` for CloudNativePG provisioning. ## Reference Router Read only what the task needs: - `references/workflow.md`: intake, schema inspection, output format, and approval gates. - `references/transactional.md`: OLTP entities, relationships, constraints, indexes, soft delete, tenancy, and audit columns. - `references/analytics.md`: OLAP/star schema, facts, dimensions, SCD, summaries, and incremental refresh design. - `references/engine-notes.md`: PostgreSQL, MySQL/MariaDB, SQLite/D1, BigQuery, and MongoDB-specific design notes. - `references/migration-review.md`: migration safety, rollout sequencing, backfills, rollback, partitioning, and risk checks. - `references/design-doc.md`: compact database design document template. ## Workflow 1. Identify the database engine and context: new schema, extension of existing schema, analytics model, data import, migration review, or design doc. 2. Inspect existing schema before proposing changes when a database or repo is available. Use `vd:miudb`, the `sqlit` CLI, migrations, ORM models, dbt models, or schema files as source of truth. 3. Capture requirements before DDL: - entities and relationships - main reads/writes/reports - expected scale and growth - tenancy, permissions, privacy,...