forge-schema-design

What problem does it solve?

This Skill prevents the most common long-term database design failures by enforcing schema “hygiene” rules that stop corruption, audit gaps, and performance issues from showing up after your app grows.

Core Features & Use Cases

• Relational schema contract rules: UUIDv7/ULID primary keys, explicit foreign keys, and deliberate ON DELETE policies to keep data integrity enforceable by the database.
• Correct types and constraints: TIMESTAMPTZ for time, NUMERIC for money, TEXT (with length checks) instead of VARCHAR(255) defaults, and enums/checks/unique constraints for invariants and status fields.
• Multi-tenancy & soft delete patterns: tenant scoping, composite foreign keys where relevant, audit columns, deleted_at soft delete, and partial unique indexes that respect soft deletion.
• Verification for common violations: provides a verifier script that flags missing created_at, autoincrement-only primary keys, TIMESTAMP without time zone, FLOAT/REAL near money columns, and VARCHAR(255) catch-alls.

Quick Start

Use forge-schema-design to review your schema.sql and ensure it follows database-enforced integrity, auditability, and production-safe typing and constraints.