supabase-reference-architecture

# Supabase Reference Architecture ## Overview Production Supabase applications need more than a flat `lib/supabase.ts` file. This skill covers five enterprise architecture patterns: monorepo with shared types, multi-tenant RLS isolation, microservices with separate Supabase projects, framework integration (Next.js / SvelteKit), and operational patterns (edge functions, caching, queues, audit trails). Each pattern stands alone — pick the ones that match your scale. For the full monorepo directory layout and microservices cross-project access, see [Project Structure](references/project-structure.md). For edge functions, caching, queue, and audit trail patterns, see [Operational Patterns](references/key-components.md). ## Prerequisites - `@supabase/supabase-js` v2+ installed (`npm install @supabase/supabase-js`) - Supabase CLI installed (`npm install -g supabase`) - A Supabase project at [supabase.com/dashboard](https://supabase.com/dashboard) - Familiarity with `supabase-install-auth` (project URL, anon key, service role key) - PostgreSQL basics (RLS policies, triggers, functions) ## Instructions ### Step 1: Client Singleton — The Foundation Every app in the monorepo imports from a shared package instead of creating its own client. This guarantees a single source of truth for the URL, keys, and type definitions. ```typescript // packages/supabase/src/client.ts import { createClient, SupabaseClient } from '@supabase/supabase-js' import type { Database } from './database...