supabase-skills plugin for AI coding agents
Supabase skills for Postgres, Auth, Edge Functions, the JS SDK, and the CLI.
- Works with
- Includes
- 4 skills
- Version
- 1.1.1
- License
- MIT
claude plugin install supabase-skills@claude-settingsWhat's inside
Each skill ZIP works in ChatGPT and Claude.ai. Read the source before you upload it.
supabase
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); debugging and troubleshooting errors or unexpected behavior on Supabase projects (HTTP errors, Postgres errors, RLS surprises, permission denied, schema cache issues, timeouts, Edge Function crashes, Realtime drops, Storage failures) and reading or querying logs (Logs Explorer, ClickHouse).
supabase-cli
This skill should be used when user asks to “use supabase CLI”, “supabase init”, “supabase start”, “run migrations”, “deploy edge functions”, “manage Supabase project”, or works with the supabase command-line tool for local development and project management.
supabase-js
This skill should be used when user asks to “use supabase-js”, “query Supabase database”, “supabase auth”, “supabase storage”, “supabase realtime”, “supabase edge functions”, or works with the @supabase/supabase-js JavaScript/TypeScript SDK.
supabase-postgres-best-practices
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.