What problem does it solve? Writing server-side Supabase code traditionally requires manual client creation, auth header forwarding, CORS handling, and direct use of legacy anon/service_role keys. This Skill guides you to use the @supabase/server package correctly, eliminating boilerplate and preventing deprecated patterns. ## Core Features & Use Cases - Auth Mode Configuration: Correctly apply the four auth modes (user, publishable, secret, none), including array syntax and named keys like secret:automations. - Framework Integration: Wire up withSupabase for Supabase Edge Functions (Deno), Cloudflare Workers, and Hono apps, or compose with @supabase/ssr for Next.js and other cookie-based frameworks. - Legacy Migration: Convert Deno.serve, esm.sh imports, SUPABASE_ANON_KEY/SUPABASE_SERVICE_ROLE_KEY usage, and deprecated allow: config to modern patterns. - Use Case: When building a Stripe webhook Edge Function, the Skill directs you to use auth: 'none' with signature verification, disable verify_jwt in supabase/config.toml, and use ctx.supabaseAdmin for database writes. ## Quick Start Ask the AI to write a Supabase Edge Function that uses @supabase/server with user auth to query a database table.