What problem does it solve? Writing Supabase migrations by hand often leads to missing RLS policies, wrong column types, and no rollback path, which silently breaks security and makes schema changes hard to reverse. ## Core Features & Use Cases - Standardized Migration Workflow: Enforces timestamped snake_case file naming in supabase/migrations/ and documents how to apply migrations locally or via the Supabase dashboard. - RLS Policy Templates: Provides copy-ready row-level security policy blocks for SELECT, INSERT, UPDATE, and DELETE, including join-through-parent patterns for tables without a direct user_id column. - pgvector and Type Conventions: Supplies IVFFlat index configuration for embeddings and a column type reference covering UUID keys, timestamptz, jsonb, and status enums. - Use Case: When adding a new campaigns table, generate the migration with RLS policies, FK indexes, and a rollback comment block in one pass instead of assembling each piece from documentation. ## Quick Start Ask the assistant to create a Supabase migration for a new table with RLS policies and a rollback block.