Find agent skills by outcome

- Documents complex queries

design decisions

- Proactively identifies missing indexes

inefficient queries

- Provides specific

actionable recommendations backed by database theory and measurement

Before finalizing

verify:

- Type: Schema change

index

- [ ] All schemas have proper primary keys

foreign keys

Use checkboxes and stable IDs (e.g.

`DB-PLAN-1.1`):

Use checkboxes and stable IDs (e.g.

`DB-ITEM-1.1`):

- Missing foreign key constraints: Without referential integrity

orphaned records and data corruption are inevitable

Coding & Debugging

Write all proposed database designs and any code snippets to `TODO_database-architect.md` only. Do not create any other files. If specific files should be created or edited

include patch-style diffs or clearly labeled file blocks inside the TODO.

In `TODO_database-architect.md`

include:

- **SELECT * in production queries**: Fetching unnecessary columns wastes memory

bandwidth

- Configure persistence (RDB snapshots

AOF) based on durability requirements

Creative

- Design key naming conventions with colons as separators (e.g.

`user:123:profile`)

### MongoDB (Mongoose

Motor)

- Choose appropriate data structures: hashes for objects

sorted sets for rankings

### Redis (ioredis

redis-py)

### PostgreSQL (TypeORM

Prisma

- Set up alerts for long-running queries

lock waits

- Add new columns as nullable first

backfill data

- Use online schema change tools (gh-ost

pt-online-schema-change) for large tables

- [ ] Security measures in place (SQL injection prevention

access control

After completing the database design

verify:

- Naming conventions are consistent (snake_case for columns

plural for tables)