What problem does it solve?
This Skill helps you implement and debug Supabase functionality correctly and securely across auth, RLS, migrations, and SDK/runtime integrations so you don’t ship broken or unsafe code.
Core Features & Use Cases
- Supabase library selection: Choose the right client for the security model (browser vs Next.js SSR vs backend) and avoid unsafe mismatches between cookie auth and JWT flows.
- @supabase/server auth modes: Use
withSupabase with clear auth modes (user, none, secret, publishable, and named variants) and correct header/credential handling.
- Operational safety for changes: Apply RLS-by-default guidance, verify fixes with test queries, and use safe iteration practices for schema changes.
- Runtime integration guardrails: Handle Edge Functions, Workers, connection pooling ports, pgvector/Realtime/Storage/Queues patterns, and common production gotchas (e.g., Edge JWT checks, CSP/WebSocket issues).
Quick Start
Use the supabase skill to implement an authenticated Edge Function with @supabase/server using auth: user, then fix any RLS or session handling issues you encounter.