veta-supabase-rls

What problem does it solve?

This Skill prevents common Supabase integration mistakes by guiding how to use the correct client in the right runtime and by reinforcing robust Row Level Security (RLS) so unauthorized data access is blocked by design.

Core Features & Use Cases

• Client vs server correctness: Use the browser client in client-side code and the server client for RSC/API/server actions to avoid runtime/auth bugs.
• Typed database access: Keep database types centralized to reduce circular imports and improve maintainability when writing or reviewing Supabase queries.
• RLS-first security discipline: Ensure RLS is enabled on every table, require policies for CRUD operations, and never rely on client-side checks or expose service-role credentials.
• Reliable error handling: Require checking the returned error from Supabase calls and surfacing meaningful feedback to users.

Quick Start

Review the code for any Supabase call paths and update them to use the correct client (browser vs server), enforce RLS with policies, and handle error responses consistently.