What problem does it solve? Writing ERP database objects by hand often leads to inconsistent naming, missing tenant isolation, SQL injection risks, and non-idempotent scripts. This Skill enforces strict conventions so every Stored Procedure, View, Table-Valued Function, Scalar Function, and Trigger follows the same multi-tenant, schema-prefixed standard. ## Core Features & Use Cases - Ready-to-use templates: Provides complete CREATE OR ALTER templates for INSERT, SELECT single row, paginated SELECT with filters, UPDATE, soft DELETE, CTE-based reports, Views, inline TVFs, Scalar Functions, and audit Triggers. - Strict convention enforcement: Mandates schema prefixes (finance., hr., inventory.), tenant_id filtering on every table and JOIN, explicit column aliases, SYSUTCDATETIME(), SET NOCOUNT ON, and bans SELECT * and unparameterized dynamic SQL. - Naming standards: Applies consistent prefixes such as usp_CreateInvoice, vw_InvoiceAging, tvf_InvoiceLines, fn_CalculateVAT, and trg_invoices_After_Update. - Use Case: Ask for a paginated invoice listing procedure and receive a complete finance.usp_ListInvoices with search, filters, sorting, OFFSET/FETCH pagination, and tenant isolation already built in. ## Quick Start Ask the assistant to write a stored procedure, view, function, or trigger for your ERP module, for example: create a stored procedure that lists invoices with pagination and tenant filtering.