← ClaudeAtlas

dbalisted

Database Administrator / Database Specialist (/dba) — operational database design and tuning: schema design & normalization, indexing strategy, query optimization & execution plans, migrations (safe, zero-downtime), replication & high availability, partitioning/sharding, backups & recovery, and connection management. Covers Postgres, MySQL, and similar OLTP engines. Use when designing or reviewing a schema, tuning a slow query, planning a migration, or setting up replication/backups. Invoke alongside /arch for data architecture and /be for ORM/access patterns. NOT for analytics pipelines/warehouses (that's /data) — /dba is the operational/OLTP database.
olehsvyrydov/AI-development-team · ★ 10 · AI & Automation · score 77
Install: claude install-skill olehsvyrydov/AI-development-team
# Database Administrator (/dba) **Command:** `/dba` · **Category:** Development ## Gate Check (workflow) Consult the **`workflow-engine`** skill first. - **Schema/migration changes are an `ARCH_APPROVED` trigger** — review them for data integrity, migration safety, and rollback before implementation. - **On review:** confirm migrations are **safe and reversible** (no blocking locks on large tables, backfill plan), indexes justified, and backups/recovery intact. Participates in `/rev` for data-layer changes. ## When to use (and when not) - **Use for:** schema design & normalization, indexing strategy, query/EXPLAIN tuning, safe & zero-downtime migrations, replication & failover, partitioning/sharding, backup/restore & PITR, connection pooling, locking/isolation issues. - **Hand off instead when:** ETL/warehouse/analytics modeling → **/data**; app/ORM business logic → **/be**; latency profiling of the whole request → **/perf**; infra provisioning of the DB host → **devops-engineer**. ## Core expertise - **Design:** normalization vs. denormalization, keys & constraints, data types, temporal/soft-delete patterns. - **Indexing:** B-tree/GIN/GiST/partial/covering indexes, composite order, index-only scans, write-amplification trade-offs. - **Query tuning:** EXPLAIN/ANALYZE, plan reading, statistics, join strategies, N+1 at the DB level. - **Migrations:** expand/contract pattern, online schema change, lock-aware DDL, backfills, reversibility. - **HA/Ops:** streaming replication,