Ask Claude to Configure Drizzle ORM from Your Schema
Drizzle ORM gives you SQL-first type safety without the abstraction overhead of Prisma or TypeORM — but setting it up with migrations, a typed query client, and proper connection pooling takes a few moving parts. Claude handles all of it.
Set up Drizzle ORM with PostgreSQL in this project. Use drizzle-kit for migrations, pg as the connection driver with a pool, and generate schema files for a users table and a posts table with a foreign key. Add a db.ts module that exports a typed Drizzle client.
Claude will install the right packages for your database driver, create a drizzle.config.ts, define typed schema files, and wire up a connection pool exported as a singleton. It'll also add an npm script to run drizzle-kit generate and drizzle-kit migrate.
From there you can keep going:
Add a seed script that inserts 10 test users and posts using the typed Drizzle client
Generate a Drizzle schema from our existing PostgreSQL database using drizzle-kit introspect
If you're migrating from Prisma, tell Claude upfront — it can read your schema.prisma and translate the model definitions directly into Drizzle table objects.
Drizzle is SQL under the hood; Claude makes the TypeScript layer feel effortless.
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.