supabase-schema-from-requirements

# Supabase Schema from Requirements ## Overview Translate business requirements into a production-ready Postgres schema inside Supabase. This skill covers the full path from specification document to applied migration: entity extraction, table creation with proper data types and constraints, Row Level Security policies, performance indexes, timestamp triggers, and TypeScript type generation. It is the highest-leverage activity in the early stages of any Supabase project because every downstream feature (auth, storage, realtime, edge functions) depends on well-designed tables. ## Prerequisites - Supabase CLI installed (`npm install -g supabase`) and project linked (`supabase link`) - `@supabase/supabase-js` v2+ installed in the project - Business requirements, PRD, or specification document identifying entities and access rules - Local Supabase running (`supabase start`) or a linked remote project ## Instructions ### Step 1: Parse Requirements and Create Migration Read the requirements document and extract entities, attributes, relationships, and access control rules. Map each entity to a Postgres table. **Entity extraction example** (project management app): | Entity | Key Columns | Relationships | |--------|------------|---------------| | Organization | name, slug, plan | has many Projects, has many Members | | Project | name, description, status | belongs to Organization, has many Tasks | | Task | title, priority, status, due_date | belongs to Project, assigned to ...