db-architect

To generate Drizzle ORM TypeScript schemas and migration SQL, structured data requirements must first be converted into PostgreSQL tables, foreign keys, and constraints with enforced best practices like timestamptz and bigint identity keys.

Designing a future-proof PostgreSQL schema requires reading structured data requirements to produce production-grade tables, explicit foreign key indexes, migration-safe steps, and documented design decisions with anti-pattern validation.

Yes, you need structured data requirements generated from a prior planning step before designing a PostgreSQL database schema, ensuring the resulting tables and constraints accurately match data subjects, relationships, and access patterns.

The best way to ensure migration safety when extending a PostgreSQL schema is to generate checklist-friendly migration SQL alongside the Drizzle ORM TypeScript definitions, enforcing strict conventions like bigint identity keys and explicit indexing.

Your PostgreSQL schema design needs explicit indexing for all foreign keys to enforce production-grade performance and correctness, preventing query bottlenecks and validating against known database anti-patterns.

Yes, you can review PostgreSQL schema decisions and anti-pattern validation before applying migrations by generating a dedicated SCHEMA_DECISIONS.md file that documents the rationale behind every constraint and table design choice.