neon-drizzle

Neon Drizzle Integration

Comprehensive Drizzle ORM setup for Neon databases with guided workflows.

When to Use This Skill

• Setting up Drizzle in a new project (Next.js, Vite, Express, etc.)
• Integrating Drizzle into an existing application
• Creating or modifying database schemas
• Troubleshooting migration issues

Code Generation Rules

When generating TypeScript/JavaScript code:

• BEFORE generating import statements, check tsconfig.json for path aliases (compilerOptions.paths)
• If path aliases exist (e.g., "@/": ["./src/"]), use them (e.g., import { x } from '@/lib/utils')
• If NO path aliases exist or unsure, ALWAYS use relative imports (e.g., import { x } from '../../../lib/utils')
• Verify imports match the project's configuration
• Default to relative imports - they always work regardless of configuration

Available Guides

Each guide is a complete, self-contained walkthrough with numbered phases:

• guides/new-project.md - Full setup from scratch (see: Table of Contents)
• guides/existing-project.md - Add Drizzle to running apps (see: Table of Contents)
• guides/schema-only.md - Schema creation and modification (see: Table of Contents)
• guides/troubleshooting.md - Debug common issues (organized by error type)

I'll automatically detect your context (package manager, framework, deployment target) and select the appropriate guide based on your request.

Quick Examples

Tell me what you're building - I'll handle the rest:

• "Setup Drizzle for my Next.js blog on Vercel" → Auto-detects Vercel + Next.js → HTTP adapter
• "Add Drizzle to my Express API" → Auto-detects Node.js server → WebSocket adapter
• "Create a users table with auth fields" → Loads schema guide → Generates schema

Reference Documentation

For deeper technical details (loaded on-demand):

• references/adapters.md - HTTP vs WebSocket decision guide
• references/migrations.md - Migration patterns and troubleshooting
• references/query-patterns.md - Example queries and best practices