What problem does it solve? Writing database migrations and stored procedures by hand often leads to inconsistent naming, missing tenant isolation columns, and non-idempotent scripts that break deployments. This Skill enforces a strict, repeatable convention for generating DbUp-compatible SQL files for a modular ERP system. ## Core Features & Use Cases - DDL Migration Generation: Creates versioned migration files (CREATE TABLE, ALTER TABLE, CREATE INDEX, CREATE SCHEMA) with the YYYYMMDD_NNN_Description naming convention, run once by DbUp. - Idempotent Stored Procedures: Generates CREATE OR ALTER stored procedures in a separate folder that DbUp re-runs on every deploy. - Convention Enforcement: Applies snake_case object naming, mandatory tenant_id on every table, tenant-first composite indexes, and a hybrid PK strategy (UUIDv7 for aggregate roots, BIGINT IDENTITY for child/audit tables). - Use Case: When adding a new Invoices module to the ERP, ask for the table, indexes, and creation stored procedure, and receive ready-to-commit SQL files placed in the correct Migrations and StoredProcedures directories. ## Quick Start Ask the assistant to create a new migration for an invoices table with its indexes and a usp_CreateInvoice stored procedure following the project conventions.