Supabase Integration Expert
Guide Supabase database, Auth, RLS, Realtime, Storage, Edge Functions, and pgvector work with security-first defaults.
Fast Workflow
- Identify the Supabase surface: schema/RLS, Auth, SSR cookies, Realtime, Storage, Edge Functions, local CLI, or vector search.
- Inspect migrations, generated database types, client/server Supabase helpers, auth middleware, and existing policy style before editing.
- Treat RLS as mandatory for user data; pair every table change with policies, indexes, and tests or SQL checks where practical.
- Keep service-role usage server-only and narrow, and prefer typed clients generated from the database schema.
- For current API details, read local docs if present or official Supabase docs before changing auth, RLS, or production data paths.
Detailed Reference
Read references/full-guide.md when you need schema/RLS examples, auth flows, SSR helpers, realtime/storage patterns, edge functions, pgvector, testing, and local development commands. Keep this entrypoint loaded first, then load only the reference sections relevant to the task.
Documentation
Run npx agent-starter docs pull supabase in a Claude install, or pull/browse official Supabase docs for the target environment.
Safety Checks
- Do not invent product limits, API behavior, prices, compliance requirements, or security guarantees.
- Keep secrets server-side and use environment variables for credentials.
- Prefer the simplest supported integration path that satisfies the product requirement.
1---2name: supabase3description: Supabase integration expert — Postgres schema design with RLS policies, Auth (email/OAuth/magic link, JWT claims), Realtime (Postgres changes, Broadcast, Presence), Storage (buckets + RLS), Edge Functions (Deno runtime, secrets, scheduled jobs), pgvector for embeddings, and client libraries (`@supabase/supabase-js`, `@supabase/ssr` for Next.js SSR). Invoke when user mentions Supabase, PostgreSQL + RLS, Supabase Auth, realtime subscriptions, Edge Functions, or pgvector. Example queries — "write an RLS policy so users only see their own rows", "set up Google OAuth with Supabase Auth and SSR cookies", "subscribe to INSERTs on a table from a React component", "store embeddings in pgvector and do similarity search".4---56# Supabase Integration Expert78Guide Supabase database, Auth, RLS, Realtime, Storage, Edge Functions, and pgvector work with security-first defaults.910## Fast Workflow11121. Identify the Supabase surface: schema/RLS, Auth, SSR cookies, Realtime, Storage, Edge Functions, local CLI, or vector search.132. Inspect migrations, generated database types, client/server Supabase helpers, auth middleware, and existing policy style before editing.143. Treat RLS as mandatory for user data; pair every table change with policies, indexes, and tests or SQL checks where practical.154. Keep service-role usage server-only and narrow, and prefer typed clients generated from the database schema.165. For current API details, read local docs if present or official Supabase docs before changing auth, RLS, or production data paths.1718## Detailed Reference1920Read `references/full-guide.md` when you need schema/RLS examples, auth flows, SSR helpers, realtime/storage patterns, edge functions, pgvector, testing, and local development commands. Keep this entrypoint loaded first, then load only the reference sections relevant to the task.2122## Documentation2324Run `npx agent-starter docs pull supabase` in a Claude install, or pull/browse official Supabase docs for the target environment.2526## Safety Checks2728- Do not invent product limits, API behavior, prices, compliance requirements, or security guarantees.29- Keep secrets server-side and use environment variables for credentials.30- Prefer the simplest supported integration path that satisfies the product requirement.
tuyv