drizzle

Registers Drizzle ORM patterns and migration workflow metadata for stack composition.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/leonardoacosta/skills --skill drizzle-leonardoacosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drizzle
Source: https://github.com/leonardoacosta/skills/tree/main/t3-stack-kit/skills/drizzle
Command: npx skills add https://github.com/leonardoacosta/skills --skill drizzle-leonardoacosta

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about drizzle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add Drizzle ORM standards to a T3 monorepo?

Enable the drizzle skill during stack composition so compose_stack registers its metadata and gate. The skill then points to t3-code-patterns for package layout and turbo tasks, and to drizzle-best-practices for migration policy.

What is the Drizzle migration policy in this stack?

The policy is migration-based only: schema changes go through drizzle-kit generated migrations, and db:push is never used. The full rationale and workflow live in the drizzle-best-practices skill under Migration Safety.

Why does compose_stack fail without the drizzle skill?

compose_stack hard-fails without this registration because the skill's frontmatter carries required metadata such as category, level, gate, and allowed tools. The body is intentionally minimal since the frontmatter is the product.

Where is the actual Drizzle schema design guidance?

Schema design and query patterns live in the database-schema-designer skill, not here. This skill only registers composition metadata and routes to the authoritative references for schema, monorepo wrapping, and migrations.

What validation gate does the drizzle skill enforce?

The declared gate is bunx drizzle-kit check, which validates the Drizzle configuration and schema during composition. The skill also restricts tools to Read, Glob, and Grep.