neon-postgres
Optimized configuration patterns for Neon serverless Postgres, including Drizzle/Prisma integration.
Install
mkdir -p .claude/skills/neon-postgres && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6793" && unzip -o skill.zip -d .claude/skills/neon-postgres && rm skill.zipInstalls to .claude/skills/neon-postgres
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Expert patterns for Neon serverless Postgres, branching, connection pooling, and Prisma/Drizzle integration Use when: neon database, serverless postgres, database branching, neon postgres, postgres serverless.Key capabilities
- →Configure Prisma with connection pooling
- →Implement Drizzle serverless drivers
- →Manage database branching
- →Set up PgBouncer
How it works
It provides patterns for Neon serverless Postgres, including connection pooling and ORM integration.
Inputs & outputs
When to use neon-postgres
- →Configuring Prisma with Neon connection pooling
- →Setting up serverless HTTP drivers for Drizzle
- →Managing database branches for development
About this skill
Neon 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 |
When not to use it
- →Non-Postgres databases
- →Local-only development without Neon
Prerequisites
Limitations
- →Requires Neon infrastructure
- →Specific to Postgres
How it compares
It offers expert-vetted patterns for serverless Postgres rather than generic database setup.
Compared to similar skills
neon-postgres side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| neon-postgres (this skill) | 1 | 6mo | No flags | Intermediate |
| drizzle-orm | 32 | 2mo | No flags | Intermediate |
| event-store-design | 5 | 2mo | No flags | Advanced |
| backend-development | 17 | 4mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by davila7
View all by davila7 →You might also like
drizzle-orm
EpicenterHQ
Drizzle ORM patterns for type branding and custom types. Use when working with Drizzle column definitions, branded types, or custom type conversions.
event-store-design
wshobson
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
backend-development
skillcreatorai
Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.
postgresql
sickn33
Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features
epic-database
epicweb-dev
Guide on Prisma, SQLite, and LiteFS for Epic Stack
sql-translation
tidyverse
Guide for adding SQL function translations to dbplyr backends. Use when implementing new database-specific R-to-SQL translations for functions like string manipulation, date/time, aggregates, or window functions.