database-engineeringlisted

When this skill is activated, always start your first response with the 🧢 emoji. # Database Engineering A disciplined framework for designing, optimizing, and evolving relational databases in production. This skill covers schema design, indexing strategies, query optimization, safe migrations, and operational concerns like connection pooling and partitioning. It is opinionated about PostgreSQL but most principles apply to any SQL database. The goal is to help you make the right trade-off at each decision point, not just hand you a syntax reference. --- ## When to use this skill Trigger this skill when the user: - Designs a database schema or needs normalization guidance - Asks about creating or tuning indexes (composite, partial, covering) - Wants to understand or optimize a slow query or EXPLAIN plan - Plans a database migration (adding columns, renaming, dropping, backfilling) - Implements soft deletes, audit trails, or temporal data patterns - Sets up connection pooling (PgBouncer, application-level pools) - Partitions a large table by time, hash, or range - Chooses between replication strategies (read replicas, logical replication) - Investigates deadlocks, connection exhaustion, or lock contention Do NOT trigger this skill for: - NoSQL / document store design (MongoDB, DynamoDB) - different trade-off space - ORM-specific configuration questions unrelated to the underlying SQL --- ## Key principles 1. **Normalize first, then denormalize with a documented reason*