What problem does it solve? Developers building Next.js 15 applications with Supabase often struggle to choose between Server and Client Components, pick the correct Supabase client for each environment, and avoid security mistakes like leaking the Service Role Key or passing full user objects to the client. ## Core Features & Use Cases - Component Decision Tree: A step-by-step guide to decide between Server Components and Client Components based on interactivity and data-fetching needs. - Implementation Patterns: Ready-to-use templates for Server Component data fetching, Client Component interactivity, Server Actions for mutations, and Route Handlers. - Security Checklist: Enforces correct Supabase client selection, getUser() over getSession(), minimal data passing, and RLS policy verification. - Use Case: When building a recipe dashboard page, use this Skill to fetch data in a Server Component with @/lib/supabase/server, pass only required fields to an interactive Client Component, and handle form submissions through a secure Server Action with revalidatePath. ## Quick Start Ask the agent to implement a Next.js page that fetches data from Supabase and includes an interactive save button following the supabase_patterns guidelines.