secondsky/claude-skills / plugins/drizzle-orm-d1/skills/drizzle-orm-d1
drizzle-orm-d1
Verified| Type-safe ORM for Cloudflare D1 databases using Drizzle. Use when: building D1 database schemas, writing type-safe SQL queries, managing migrations with Drizzle Kit, defining table relations, implementing prepared statements, using D1 batch API, or encountering D1_ERROR, transaction errors, foreign key constraint failures, or schema inference issues.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.2 KB |
| references/common-errors.md | markdown | 5.3 KB |
| references/error-catalog.md | markdown | 7.9 KB |
| references/links-to-official-docs.md | markdown | 1.8 KB |
| references/migration-workflow.md | markdown | 2.7 KB |
| references/query-builder-api.md | markdown | 3.9 KB |
| references/schema-patterns.md | markdown | 3.4 KB |
| references/wrangler-setup.md | markdown | 2.7 KB |
| scripts/check-versions.shexecutable | script | 1017 B |
| templates/basic-queries.ts | script | 7.5 KB |
| templates/basic-schema.ts | script | 2.9 KB |
| templates/client.ts | script | 2.2 KB |
| templates/cloudflare-worker-integration.ts | script | 7.7 KB |
| templates/drizzle.config.ts | script | 2.2 KB |
| templates/migrations/0001_example.sql | other | 2.1 KB |
| templates/package.json | manifest | 1.1 KB |
| templates/prepared-statements.ts | script | 7.3 KB |
| templates/relations-queries.ts | script | 6.8 KB |
| templates/schema.ts | script | 6.5 KB |
| templates/transactions.ts | script | 6.8 KB |
references/wrangler-setup.md
View on GitHub# Wrangler Setup for D1 and Drizzle
Complete guide to configuring Wrangler for D1 databases with Drizzle ORM.
---
## wrangler.jsonc Configuration
```jsonc
{
"name": "my-worker",
"main": "src/index.ts",
"compatibility_date": "2025-10-11",
// Node.js compatibility (recommended for Drizzle)
"compatibility_flags": ["nodejs_compat"],
// D1 database bindings
"d1_databases": [
{
// Binding name (used as env.DB in code)
"binding": "DB",
// Database name
"database_name": "my-database",
// Production database ID (from wrangler d1 create)
"database_id": "your-production-database-id",
// Local database ID (for development)
"preview_database_id": "local-db",
// Migrations directory (Drizzle generates here)
"migrations_dir": "./migrations"
}
]
}
```
---
## Environment Variables
Create `.env` file (never commit):
```bash
CLOUDFLARE_ACCOUNT_ID=your-account-id
CLOUDFLARE_DATABASE_ID=your-database-id
CLOUDFLARE_D1_TOKEN=your-api-token
```
---
## Wrangler Commands
```bash
# Create database
wrangler d1 create my-database
# List databases
wrangler d1 list
# Database info
wrangler d1 info my-database
# Apply migrations (local)
wrangler d1 migrations apply my-database --local
# Apply migrations (remote)
wrangler d1 migrations apply my-database --remote
# Execute SQL directly (local)
wrangler d1 execute my-database --local --command="SELECT * FROM users"
# Execute SQL directly (remote)
wrangler d1 execute my-database --remote --command="SELECT * FROM users"
```
---
## Local vs Remote
**Local Development** (`--local`):
- Uses SQLite file in `.wrangler/state/v3/d1/`
- Fast, no network latency
- Data persists between `wrangler dev` sessions
- Perfect for development and testing
**Remote/Production** (`--remote`):
- Uses actual D1 database in Cloudflare
- Subject to rate limits
- Production data
- Use for staging/production environments
**Always test locally first!**
---
## Migration Workflow
```bash
# 1. Make schema changes in src/db/schema.ts
# 2. Generate migration
npm run db:generate # or: drizzle-kit generate
# 3. Apply to local database
npm run db:migrate:local # or: wrangler d1 migrations apply DB --local
# 4. Test locally
npm run dev
# 5. Deploy code
npm run deploy
# 6. Apply to production database
npm run db:migrate:remote # or: wrangler d1 migrations apply DB --remote
```
---
## Important Notes
1. **migrations_dir**: Must point to where Drizzle generates migrations (usually `./migrations`)
2. **Binding name**: Must match in wrangler.jsonc, Env interface, and code
3. **Local first**: Always test migrations locally before remote
4. **Never commit**: Never commit database IDs or API tokens to version control
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |