database-engineeringlisted

# Database Engineering (Canonical) **Expertise: expert.** Aliases: `database`, `postgresql`, `sql`, `migrations`, `dba`, `schema-design`. Data-layer playbook for the **Database Engineer** role. It does not replace `supabase-cli` (Supabase runtime) or the global `security` rule (auth/PII policy). ## When to use - Desain/ubah schema, ERD, **relasi**, constraint, **index** - Migration / seeder (Laravel `database/migrations`, SQL generik, dll.) - **Performance**: pagination di DB, anti-N+1, EXPLAIN, index strategy, transaksi pendek - Objek DB lanjutan: **VIEW**, **TRIGGER**, **FUNCTION** / procedure (bila stack mengizinkan) - Tabel **mapping / junction / `_mp`** (N:M dan pemetaan referensi) - Integritas data, unique/FK, cascade, soft-delete vs hard-delete - PostgreSQL (default Phase 1 house) atau MySQL/MariaDB bila stack project memakai itu - Review perubahan DB sebelum Backend mengikat API ## When not to use - Hanya business logic / API contract → Backend / Tech Lead - Hanya UI list/filter → Frontend - Operasi container DB saja tanpa schema → `container-docker-ops` - Edge functions / Supabase CLI spesifik → `supabase-cli` - Kebijakan auth/secret global tanpa perubahan schema → `security` - Memindahkan seluruh domain workflow ke trigger tanpa ADR (anti-pattern) ## Procedure 1. **Context** — Baca SRS/architecture data (`docs/architecture/database-design.md` bila ada), `PROJECT.md`, rule `database` + `security` + `coding`. 2. **Model** — Entitas, PK/FK, kardinalitas, normal