What problem does it solve? Teams building on Postgres or Supabase often ship tables without row-level security, apply inconsistent naming, or misuse JSON columns for data that later needs filtering. This Skill provides concrete defaults for schema design so the data layer stays secure, consistent, and queryable. ## Core Features & Use Cases - Secure-by-default schema design: Enforces row-level security with explicit policies on every user or tenant table, and keeps the service-role key server-side only. - Tables vs. JSON decision guidance: Helps decide when normalized columns are required versus when a JSON document store is appropriate, based on query patterns. - Naming, relationships, and indexing standards: Applies one consistent naming convention, correct foreign keys and cardinality, and indexes aligned to real filter and join patterns. - Use Case: When creating a new multi-tenant SaaS schema on Supabase, use this Skill to define tables with RLS policies scoped per tenant, proper foreign keys, and versioned migration scripts. ## Quick Start Use the supabase-data-design skill to design a schema for my app's users, projects, and billing tables with row-level security enabled.
