Supabase Complete Documentation

## Quick judgement A high-quality, comprehensive Supabase reference skill that is well-structured and broadly suitable as the *primary* documentation source for any Supabase-related task. It is especially strong for design/explanation, code generation with Supabase SDKs, and troubleshooting. Some residual safety risk remains around destructive commands or configuration changes, so agents should treat all commands as suggestions and surface them to users for review rather than execute them. ### Key strengths - **End-to-end coverage**: Auth, database, storage, edge functions, realtime, AI/embeddings, cron, queues, platform management, self-hosting, local development, and framework integrations. - **Good navigability**: Clear directory structure and a “Common Tasks → Directory to Check” mapping, which agents can use to quickly focus on relevant sections. - **Operational depth**: Includes performance tuning, logs/monitoring, backups, migrations, CI/CD, troubleshooting, and error codes, enabling agents to help with real-world production issues. - **Safety-conscious**: Prominent security notice that commands are for reference only and must not be auto-run without explicit user approval. ### Main risks / limitations - **Command misuse risk**: Docs likely contain SQL, CLI, and shell commands (including potentially destructive ones). If an agent is connected to a runtime, it must *not* auto-execute these; it should: - Present commands as proposed steps, clearly label them as unexecuted, and - Ask the user for explicit confirmation and context (e.g., environment, backups) before any execution. - **Version drift**: As Supabase evolves, some details or APIs may become outdated. Agents should avoid assuming the docs are always perfectly up to date; where behavior in the user’s project contradicts the docs, prioritize empirical feedback from the user. - **Context size / latency**: The documentation set is likely large. Retrieval quality and latency will depend on how the host system chunks and indexes these files. ### Recommended scenarios Use this skill by default when: - Designing or revising **Supabase auth flows**, including OAuth, magic links, phone/SMS, SSO/SAML, and MFA. - Creating or updating **database schemas, RLS policies, functions, triggers**, or planning **migrations**. - Implementing **file storage**, CDN, and access control patterns in Supabase. - Building and deploying **edge functions** or wiring them to auth and database operations. - Setting up or debugging **realtime** subscriptions, presence, or broadcast features. - Implementing **AI/vector search** with pgvector and RAG-style patterns on Supabase. - Working on **self-hosted** Supabase, local development, CLI usage, or CI/CD pipelines. - **Troubleshooting errors** using the troubleshooting and errorCodes references. Use with extra caution (and explicit user approval) when: - Proposing SQL or CLI commands that modify schemas, RLS, or production data. - Guiding backup/restore, replication changes, or platform-level operations (billing, projects, organizations). - Suggesting cron/queue configurations that could generate large workloads or costs.