What problem does it solve? Teams writing Drizzle ORM schemas and queries often drift into inconsistent patterns—composite primary keys that block future scope changes, fragile relational API queries, loosely typed JSONB columns, and speculative fields—leading to painful migrations and hard-to-review code. ## Core Features & Use Cases - Schema Conventions: Standardizes pgTable definitions with surrogate primary keys, unique indexes, snake_case naming, timestamp helpers, and typed JSONB columns. - Query Style Enforcement: Mandates the db.select() builder API over the relational db.query API, with patterns for joins, aggregations, one-to-many fetches, and raw SQL fallbacks like recursive CTEs. - Migration-Safe Design Rules: Guides decisions on enums, sentinel values, foreign keys, and junction tables so schemas evolve without destructive rebuilds. - Use Case: When adding a new workspace-scoped table with a many-to-many relation, apply this Skill to generate a surrogate-PK schema with a unique index, typed columns, and a matching select-plus-join query that passes code review. ## Quick Start Use the drizzle skill to write a pgTable schema and select query for a new workspace settings table following the project conventions.