Supabase Postgres Best Practices

by supabasec9be0e931b79MITListed Oct 8, 2026Updated Oct 8, 2026

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.

Instructions onlySoftware Development Data & Analytics

AI-generated overview

Reference rules for writing, reviewing and optimizing Postgres schemas, queries, indexes, RLS and connections.

What it does: Provides a prioritized set of Postgres best-practice rules across eight categories: query performance, connection management, security and RLS, schema design, concurrency and locking, data access patterns, monitoring and diagnostics, and advanced features. Each rule file explains why the topic matters and shows incorrect versus correct SQL examples, with optional EXPLAIN output and metrics. It is an instructions-only reference and produces no files or scripts.
When to use it: Load it before writing or changing anything in a Postgres database, including tables, columns, migrations, RLS policies, indexes, triggers, functions, queues, scheduled jobs, vector search, or data imports. Also use it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant.
Requirements: No tools, packages or credentials are required; it is documentation only and ships no scripts. Network access is not needed, though the document links to external Postgres and Supabase documentation.