supabase-patternslisted

# Supabase Patterns Skill Universal patterns for working with Supabase in any project. Covers RLS policies, realtime, storage, edge functions, and migrations. ## Design Principle This skill is **framework-generic**. It provides universal Supabase patterns: - NOT tailored to Book-Vetting, ocr-service, or any specific project - Covers common patterns applicable across all Supabase projects - Project-specific configurations go in project-specific skills ## Variables | Variable | Default | Description | |----------|---------|-------------| | SUPABASE_DIR | supabase | Directory for Supabase config | | ENFORCE_RLS | true | Require RLS on all tables | | REALTIME_ENABLED | auto | Auto-detect realtime tables | ## Instructions **MANDATORY** - Follow the Workflow steps below in order. 1. Check Supabase project configuration 2. Review existing RLS policies 3. Follow security-first patterns 4. Keep migrations organized ## Red Flags - STOP and Reconsider If you're about to: - Create a table without RLS policies - Use service role key in client-side code - Skip migrations for schema changes - Expose sensitive data in realtime **STOP** -> Add RLS policies -> Use appropriate keys -> Then proceed ## Cookbook ### RLS Policies - IF: Creating or modifying RLS policies - THEN: Read and execute `./cookbook/rls-policies.md` ### Realtime Subscriptions - IF: Setting up realtime features - THEN: Read and execute `./cookbook/realtime-subscriptions.md` ### Storage Patterns - IF: Working wi