Supabase operator

Configure and debug Supabase authentication, covering email and password sign-in, magic links, OAuth providers, redirect URL allow lists, session cookies and server-side refresh, validating a user on the server, the auth.users table and a linked profiles row, app metadata versus user metadata, email templates, and administrative user operations. Use when sign-in must be added or repaired, when a redirect is rejected, when a session is lost on refresh, or when a user record must be created or inspected.

Answer quick Supabase questions with a compact reference for CLI commands, local stack control, migrations and database diffing, type generation, client query and filter syntax, auth calls, storage calls, edge function commands, and the key and URL differences between environments. Use when someone asks which Supabase CLI command or client call to use, or wants a fast lookup rather than a guided workflow.

Query and change Postgres inside a Supabase project, covering psql and Studio access, schema inspection, scoped reads and writes, transactions, database functions and triggers, extensions, generated columns, explain plans, and the difference between acting through the client and acting as a superuser. Use when data must be read or corrected, when a query is slow, when a database function or trigger is needed, or when schema details must be inspected.

Write, run, and deploy Supabase edge functions, covering the Deno runtime and imports, local serving with secrets, request handling and CORS, calling the database with the caller's session or the service role, verifying the JSON Web Token or accepting unauthenticated webhooks, scheduling, logs, and deployment to a linked project. Use when a server-side endpoint is needed, when a function fails locally or after deploy, or when a webhook receiver must be built.

Inspect the Supabase CLI version, whether a project directory is initialized and linked, which remote project reference is targeted, the local stack status and its URLs, which keys and URLs the application reads, migration state on both sides, and the Docker prerequisite, without changing anything. Use before a Supabase operation, when it is unclear whether a command hits local or remote, or when the user asks whether Supabase is set up.

Connect Supabase to the systems around it, covering client libraries per framework and rendering model, server-side session handling, direct Postgres access from an ORM alongside the client, realtime subscriptions, database webhooks to external services, continuous integration with a throwaway database, branch environments, and third-party auth providers. Use when an application must talk to Supabase, when an ORM must coexist with the client, when realtime updates are needed, or when a pipeline must run against a real schema.

Create, review, and apply Supabase migrations, covering handwritten migration files, generating one from a schema diff, local reset and replay, seed data, remote push and its approval boundary, drift between local and remote, repairing migration history, and safe patterns for destructive or long-running schema changes. Use when the schema must change, when a Studio change needs capturing as a file, when local and remote have diverged, or before pushing anything to a linked project.

Discover, compatibility-check, install, update, or explain Supabase's first-party agent skills. Use when asked about Supabase native skills, supabase/agent-skills, Postgres best-practice skills, agent setup, or compatibility with the project's Supabase CLI, client, and Postgres versions.

Write and verify Postgres row level security policies in Supabase, covering enabling security per table, separate policies per command, using and check expressions, the auth helper functions, joins and membership checks, performance of policy predicates, security definer helper functions, and testing a policy from the perspective of an anonymous, wrong, and correct user. Use when a table must be protected, when a query returns no rows or too many, or when a policy must be reviewed before shipping.

Set up a Supabase project from zero, covering CLI installation, project initialization, linking to a remote project reference, starting the local Docker stack, creating the environment files for local and hosted use, generating database types, and separating the anon key from the service role key. Use when a repository has no Supabase directory, when the local stack must be started for the first time, when a project must be linked, or when the user asks how to get Supabase running.

Create and operate Supabase storage buckets, covering public versus private buckets, storage access policies on the objects table, uploads with content type and cache control, signed URLs and signed upload URLs, path conventions that scope files per user, listing and moving objects, image transformations, and deletion. Use when files must be uploaded or served, when a bucket must be secured, when an upload is rejected, or when a file URL returns nothing.

Diagnose Supabase failures from reproducible evidence, covering local stack and Docker problems, wrong key or wrong environment, empty results caused by row level security, migration drift and failed pushes, session loss and redirect rejections, storage upload and URL failures, edge function and CORS errors, connection exhaustion, and stale generated types. Use when a Supabase call errors or returns nothing, when a migration push fails, when sign-in or a redirect breaks, or when something works locally but not when deployed.