Supabase

Reviews your query, schema, or config against Supabase production patterns and suggests indexing, query rewrites, or structural changes that cut latency without a migration.

Answers questions about Supabase setup, auth flows, database queries, edge functions, and client library integration across Next.js, React, SvelteKit, Astro, and Remix.

Walks you through defining a problem, structuring the solution, writing triggers and workflows, and packaging it as a reusable skill that Claude can run independently.

Sets up Vitest with mocks, fixtures, and coverage config. Writes Jest-compatible tests that run fast enough to keep in your hot-reload loop.

Analyzes a messy React file and suggests composition patterns (compound, render props, hooks) with before/after examples that actually reduce prop drilling and nesting.

Use when planning or writing server-side code that uses `@supabase/server` — Edge Functions, Hono apps, webhook handlers, or any backend that creates Supabase clients or validates inbound auth. Trigger **before** writing or modifying any file that imports from `@supabase/server` (or sub-paths like `@supabase/server/core`); calls `withSupabase`, `createSupabaseContext`, `createAdminClient`, `createContextClient`, `verifyAuth`, `verifyCredentials`, or `extractCredentials`; configures an `auth:` mode (`'none'` | `'publishable'` | `'secret'` | `'user'`, or keyed variants like `'secret:*'`); or lives under `supabase/functions/` and authenticates an inbound request. Also trigger during planning — if a plan mentions any of the above, load the skill before drafting code; do not extrapolate `auth:` values or auth modes from neighboring functions. Also trigger when you see legacy patterns to migrate to this package — `Deno.serve`, `createClient(Deno.env.get('SUPABASE_URL'))`, imports from `esm.sh/@supabase` or `deno.land/std`, usage of `SUPABASE_ANON_KEY` / `SUPABASE_SERVICE_ROLE_KEY`, or the deprecated `allow:` config option / removed `'always'` / `'public'` mode values / removed `authType` field.