Supabase postgres best practices skill

Postgres best practices maintained by Supabase, for Postgres running anywhere.

by supabase·MIT license·★ 2,694 Stars on the repo·GitHub ↗

Use now

Files of Supabase postgres best practices

supabase/main1 file shown
SKILL.md
Show the full text65 lines
supabase-postgres-best-practices/SKILL.md65 lines · 3.2 KB

Supabase Postgres Best Practices

Comprehensive performance optimization guide for Postgres, maintained by Supabase. Contains rules across 8 categories, prioritized by impact to guide automated query optimization and schema design.

When to Apply

Reference these guidelines when:

  • Writing SQL queries or designing schemas
  • Implementing indexes or query optimization
  • Reviewing database performance issues
  • Configuring connection pooling or scaling
  • Optimizing for Postgres-specific features
  • Working with Row-Level Security (RLS)

Rule Categories by Priority

Priority Category Impact Prefix
1 Query Performance CRITICAL query-
2 Connection Management CRITICAL conn-
3 Security & RLS CRITICAL security-
4 Schema Design HIGH schema-
5 Concurrency & Locking MEDIUM-HIGH lock-
6 Data Access Patterns MEDIUM data-
7 Monitoring & Diagnostics LOW-MEDIUM monitor-
8 Advanced Features LOW advanced-

How to Use

Read individual rule files for detailed explanations and SQL examples:

references/query-missing-indexes.md
references/query-partial-indexes.md
references/_sections.md

Each rule file contains:

  • Brief explanation of why it matters
  • Incorrect SQL example with explanation
  • Correct SQL example with explanation
  • Optional EXPLAIN output or metrics
  • Additional context and references
  • Supabase-specific notes (when applicable)

References

1---
2name: supabase-postgres-best-practices
3description: "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."
4license: MIT
5metadata:
6 author: supabase
7 version: "1.1.1"
8 organization: Supabase
9 date: January 2026
10 abstract: Comprehensive Postgres performance optimization guide for developers using Supabase and Postgres. Contains performance rules across 8 categories, prioritized by impact from critical (query performance, connection management) to incremental (advanced features). Each rule includes detailed explanations, incorrect vs. correct SQL examples, query plan analysis, and specific performance metrics to guide automated optimization and code generation.
11---
12 
13# Supabase Postgres Best Practices
14 
15Comprehensive performance optimization guide for Postgres, maintained by Supabase. Contains rules across 8 categories, prioritized by impact to guide automated query optimization and schema design.
16 
17## When to Apply
18 
19Reference these guidelines when:
20- Writing SQL queries or designing schemas
21- Implementing indexes or query optimization
22- Reviewing database performance issues
23- Configuring connection pooling or scaling
24- Optimizing for Postgres-specific features
25- Working with Row-Level Security (RLS)
26 
27## Rule Categories by Priority
28 
29| Priority | Category | Impact | Prefix |
30|----------|----------|--------|--------|
31| 1 | Query Performance | CRITICAL | `query-` |
32| 2 | Connection Management | CRITICAL | `conn-` |
33| 3 | Security & RLS | CRITICAL | `security-` |
34| 4 | Schema Design | HIGH | `schema-` |
35| 5 | Concurrency & Locking | MEDIUM-HIGH | `lock-` |
36| 6 | Data Access Patterns | MEDIUM | `data-` |
37| 7 | Monitoring & Diagnostics | LOW-MEDIUM | `monitor-` |
38| 8 | Advanced Features | LOW | `advanced-` |
39 
40## How to Use
41 
42Read individual rule files for detailed explanations and SQL examples:
43 
44```
45references/query-missing-indexes.md
46references/query-partial-indexes.md
47references/_sections.md
48```
49 
50Each rule file contains:
51- Brief explanation of why it matters
52- Incorrect SQL example with explanation
53- Correct SQL example with explanation
54- Optional EXPLAIN output or metrics
55- Additional context and references
56- Supabase-specific notes (when applicable)
57 
58## References
59 
60- https://www.postgresql.org/docs/current/
61- https://supabase.com/docs
62- https://wiki.postgresql.org/wiki/Performance_Optimization
63- https://supabase.com/docs/guides/database/overview
64- https://supabase.com/docs/guides/auth/row-level-security
65 

Discussion

Alternatives