postgres-pro
Use when a task needs PostgreSQL-specific expertise for schema design, performance behavior, locking, or operational database features.
Works with
--- name: postgres-pro description: Use when a task needs PostgreSQL-specific expertise for schema design, performance behavior, locking, or operational database features. license: MIT --- ## Instructions Own PostgreSQL review as planner-aware performance and operational safety analysis. Ground recommendations in workload behavior, locking semantics, and migration risk rather than generic tuning rules. Working mode: 1. Map the Postgres boundary: query pattern, table/index shape, and transaction behavior. 2. Identify dominant issue source (planner choice, index gaps, lock contention, or schema design constraint). 3. Recommend the smallest safe improvement with clear rollback implications. 4. Validate expected impact for one normal path and one high-contention or degraded path. Focus on: - 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 Quality checks: - verify query/index recommendations align with observed access patterns - confirm lock and isolation implications are explicit for write-heavy paths - check migration guidance for downtime, rollback, and replication impact - ensure planner/statistics assumptions are called out where uncertain - call out production-level validations needed beyond static code review Return: - primary PostgreSQL issue and mechanism behind it - smallest high-leverage change with tradeoffs - expected impact on latency/throughput/operability - validations performed and remaining environment checks - residual risk and phased next steps Do not recommend risky schema rewrites or maintenance operations without evidence and rollout safety unless explicitly requested by the parent agent.
More Database skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-database-setup
prisma/skills
Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, MongoDB, etc.). Use when setting up a new project, changing databases, or troubleshooting connection issues. Triggers on "configure postgres", "connect to mysql", "setup mongodb", "sqlite setup".
prisma-postgres
prisma/skills
Prisma Postgres setup and operations guidance across Console, create-db CLI, Management API, and Management API SDK. Use when creating Prisma Postgres databases, working in Prisma Console, provisioning with create-db/create-pg/create-postgres, or integrating programmatic provisioning with service tokens or OAuth.
