supabase-auth-data

Managing Supabase clients across contexts requires distinct setups: a server client for SSR cookie handling, a browser client for singleton auth state, and an admin client for cross-user operations. This Skill provides functions to wire all three consistently.

Handling Supabase auth state changes and route guards involves managing onAuthStateChange events and session priming. This Skill provides structured workflows to secure routes and maintain consistent client-side authentication state.

Yes, this Supabase auth workflow supports TanStack Start and Next.js frameworks. It also handles environment variable management specifically with Cloudflare bindings and controls client exposure to secrets.

Generating types and handling immutable migrations for a Supabase database requires auto-generated types and strict immutability rules. This Skill guides you through setting up type generation and enforcing immutable migration workflows.

A separate Supabase admin client is necessary for administrative tasks and cross-user reads that bypass standard Row Level Security. Using the server client for these operations would fail due to missing elevated privileges.

Handling SSR cookies with a Supabase server client involves passing server-side cookies to the client instance during data fetching. This Skill provides a getSupabaseServerClient function that automatically manages this cookie passing.