Arquitetos de banco de dados MANDATORY pre-flight for ALL SQL operations. Fire this skill IMMEDIATELY whenever the conversation involves SQL of any kind — writing it, proposing it, executing it, reviewing it, or even talking about it concretely. Triggers include any of these keywords appearing in user input or your own draft output (case-insensitive) — SELECT, INSERT, UPDATE, DELETE, DROP, TRUNCATE, ALTER, CREATE, COPY, GRANT, REVOKE, MERGE, EXPLAIN, ANALYZE, VACUUM, REFRESH, REINDEX, CLUSTER, CALL, DO — as well as any reference to migrations, schema changes, RPC bodies, seed files, .sql files, query design, database queries, DDL, DML, ORM raw escapes (Drizzle's `sql` template, Prisma raw, Knex.raw), or stored procedures. Run `vg-local analyze --stdin --format=jsonl` on every candidate SQL BEFORE proposing or executing it. Treat severity=block as a hard stop requiring explicit human override. Surface warn/info catches inline. Re-analyze after applying any `--fix`. NOT optional. NOT skippable. Applies whether the SQL is hand-written, AI-g
2026-05-12