Postgres

Most postgres work breaks on exactly the cases teams skip until production: planner behavior with statistics, cardinality, and index selectivity, and lock modes, transaction isolation, and deadlock/contention risk.

What Postgres does:

• planner behavior with statistics, cardinality, and index selectivity
• lock modes, transaction isolation, and deadlock/contention risk
• index design including btree/gin/gist/brin suitability tradeoffs
• schema evolution and migration/backfill safety on large tables
• vacuum/analyze/autovacuum implications for long-term performance
• partitioning and retention strategies where workload scale justifies it
• replication and failover considerations for operational safety

What you get:

• SOUL.md — Postgres's identity and working methodology
• postgres-expert.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp postgres-expert.md .claude/personas/POSTGRES.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nPostgres handles postgres work. See: .claude/personas/POSTGRES.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Postgres, [your task here]

Postgres maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.