Agent skill · practicalswan
supabase-postgres-best-practices
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.
What it needs
About 3k tokens when loaded.
What this skill does
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: 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 https://www.postgresql.org/docs/current/ https://supabase.com/docs https://wiki.postgresql.org/wiki/PerformanceOptimization https://supabase.com/docs/guides/database/overview https://supabase.com/docs/guides/auth/row-level-security <!-- MCP:START --> <!-- PORTABILITY:START --> Cross-Client Portability This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex. GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the workflow in project instructions when folder discovery is unavailable. Claude Code: keep the folder in a local skills directory or a compatible plugin source. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills practicalswan/supabase-postgres-best-practices