What problem does it solve? Writing database migrations by hand is error-prone: developers often forget Row Level Security policies, indexes on foreign keys, audit columns, or proper grants, leading to insecure or slow schemas. This Skill standardizes Supabase PostgreSQL migration generation so every table follows consistent naming, security, and audit conventions. ## Core Features & Use Cases - Complete Migration Scaffolding: Produces migration files with header comments, CREATE TABLE statements, RLS enablement and policies, indexes, triggers, and GRANT statements in the correct supabase/migrations/[timestamp]_[description].sql location. - DaaS Naming & Audit Conventions: Enforces snake_case plural tables, UUID primary keys, and standard audit columns (date_created, date_updated, user_created, user_updated). - Relationship & Policy Patterns: Provides ready-made templates for one-to-many foreign keys, many-to-many junction tables, and common RLS policies such as owner-only CRUD and public-read for published content. - Use Case: When adding a new blog_posts collection to a Supabase project, invoke this Skill to get a full migration including RLS policies, indexes on foreign keys, and an auto-updating date_updated trigger, then apply it with supabase db push. ## Quick Start Ask the AI to create a database migration for a new table, for example: "Create a migration for a products table with name, price, and a category foreign key."
