Supabase Boundaries

Service boundary patterns for Supabase projects.

When to Use

Use this skill only when:

• Working in a project that uses Supabase
• Creating or refactoring Supabase access code
• Enforcing a clear boundary between Supabase and the rest of the app

Non-Negotiables (MUST)

• Single boundary: All Supabase access lives in a dedicated layer (service wrappers). No direct Supabase calls from outside that layer.
• Single client: The Supabase client is created in one module; all Supabase usage goes through that client and your service wrappers.
• Focused wrappers: Keep wrappers small, focused, and typed.