About neon-postgres
A configuration skill for developers using Neon Postgres with Prisma or Drizzle. It explains connection pooling and when applications and migrations need different connection types.
Key features
- 01Configure Prisma connection pooling
- 02Use Drizzle serverless drivers
- 03Distinguish pooled and direct endpoints
- 04Explain PgBouncer pool limits
Use cases
- 01Set up Neon for a Prisma application
- 02Use Drizzle in edge or serverless environments
- 03Configure direct connections for migrations
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/neon-postgresin Claude Code to confirm it loaded.
Details
From the project READMENeon Postgres
Patterns
Prisma with Neon Connection
Configure Prisma for Neon with connection pooling.
Use two connection strings:
- DATABASE_URL: Pooled connection for Prisma Client
- DIRECT_URL: Direct connection for Prisma Migrate
The pooled connection uses PgBouncer for up to 10K connections. Direct connection required for migrations (DDL operations).
Drizzle with Neon Serverless Driver
Use Drizzle ORM with Neon's serverless HTTP driver for edge/serverless environments.
Two driver options:
- neon-http: Single queries over HTTP (fastest for one-off queries)
- neon-serverless: WebSocket for transactions and sessions
Connection Pooling with PgBouncer
Neon provides built-in connection pooling via PgBouncer.
Key limits:
- Up to 10,000 concurrent connections to pooler
- Connections still consume underlying Postgres connections
- 7 connections reserved for Neon superuser
Use pooled endpoint for application, direct for migrations.
⚠️ Sharp Edges
| Issue | Severity | Solution |
|---|---|---|
| Issue | high | See docs |
| Issue | high | See docs |
| Issue | high | See docs |
| Issue | medium | See docs |
| Issue | medium | See docs |
| Issue | low | See docs |
| Issue | medium | See docs |
| Issue | high | See docs |
Comments
Markdown supported