supabase-postgres-best-practices

Optimize Supabase PostgreSQL queries, schemas, connections, and security with rule-based guidance.

5|1|Updated Oct 18, 2019
One-click install
npx skills add https://github.com/Marshall-Hallenbeck/dot_files --skill supabase-postgres-best-practices-marshall-hallenbeck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase-postgres-best-practices
Source: https://github.com/Marshall-Hallenbeck/dot_files/tree/main/.claude/skills/postgres-best-practices
Command: npx skills add https://github.com/Marshall-Hallenbeck/dot_files --skill supabase-postgres-best-practices-marshall-hallenbeck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses common Postgres performance bottlenecks, inefficient schema designs, and connection management issues that often lead to database instability and slow query execution.

Core Features & Use Cases

  • Performance Optimization: Provides actionable rules for query tuning, index selection, and connection pooling to ensure high-throughput database operations.
  • Schema & Security Best Practices: Offers guidance on data types, constraint management, and Row-Level Security (RLS) to maintain data integrity and tenant isolation.
  • Use Case: When reviewing a slow-running query or designing a new table, use this skill to identify the optimal index type, verify if partitioning is required, or ensure RLS policies are implemented for maximum performance.

Quick Start

Use the supabase-postgres-best-practices skill to analyze the provided SQL query and suggest performance improvements based on the query performance guidelines.

Frequently Asked Questions about supabase-postgres-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I optimize a slow PostgreSQL query in Supabase?

PostgreSQL performance optimization in Supabase involves analyzing slow SQL queries to apply rule-based guidance for query tuning, optimal index selection, and connection pooling to resolve execution bottlenecks.

What are the best practices for PostgreSQL schema design and Row-Level Security?

PostgreSQL schema and security best practices dictate selecting appropriate data types, managing database constraints for data integrity, and implementing Row-Level Security policies to enforce strict tenant isolation.

When do I need database partitioning for PostgreSQL workloads?

Database partitioning for PostgreSQL workloads is needed when managing high-volume tables that degrade query performance, enabling data partitioning to maintain scalable and high-performance database architecture.

Does this database optimization guidance apply to high-throughput Supabase workloads?

Yes, this database optimization guidance applies to high-throughput Supabase workloads by providing prioritized rule-based recommendations for SQL query tuning, connection management, and scalable database architecture.

What is the best way to manage Postgres connection pooling for scalability?

Managing Postgres connection pooling for scalability requires applying connection management rules to maintain stable, high-throughput database operations and prevent database instability under heavy connection loads.