supabase-patterns

Authentication deadlocks occur when getSession is called on the client side instead of the server. Use getUser on the server and avoid getSession on the client to maintain safe session handling. This Skill consolidates proven patterns that eliminate this common pitfall in Supabase applications.

Use the admin client in API routes when you need to perform operations that should bypass row-level security constraints while preserving data security. This Skill provides guidance on adminClient usage patterns that maintain security boundaries between server and client operations.

Safe RLS-aware data access requires clear separation between server components using admin patterns and client-side operations with authenticated users. This Skill covers session handling, caching patterns, and differentiation between server and client contexts to keep RLS enforcement consistent.

MCP server access patterns provide safe methods for migrations, table management, and verification without external tooling. This Skill consolidates these patterns within standard Supabase client libraries and internal codebase practices.

Yes. Session caching and handling patterns designed for long-running operations prevent state loss while maintaining RLS compliance. This Skill documents proven session management techniques that scale reliably in production applications.