What problem does it solve? Teams composing a T3 monorepo need a registered Drizzle skill entry so the compose_stack tooling can resolve database standards, migration policy, and validation gates without duplicating schema guidance across skills. ## Core Features & Use Cases - Composition Registration: Carries the frontmatter metadata (category, level, gate, allowed tools) that compose_stack requires to include Drizzle standards in a stack. - Migration Policy Pointer: Routes users to the migration-based-only workflow (never db:push) defined in drizzle-best-practices. - Cross-Reference Hub: Directs engineers to database-schema-designer for schema design and t3-code-patterns for monorepo packaging. - Use Case: When assembling a T3 stack with Drizzle, the compose step validates this skill via the bunx drizzle-kit check gate and pulls in the linked schema and migration guidance. ## Quick Start Ask the agent to compose the T3 stack with Drizzle so the registered database standards and migration policy are applied to the project.