neon-postgres

Configure Prisma and Drizzle with Neon pooled and direct connection strings.

1|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/jokken79/YuKyuDATA-app1.0v --skill neon-postgres-jokken79
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neon-postgres
Source: https://github.com/jokken79/YuKyuDATA-app1.0v/tree/main/.agent/skills/neon-postgres
Command: npx skills add https://github.com/jokken79/YuKyuDATA-app1.0v --skill neon-postgres-jokken79

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Neon serverless Postgres integration is complex due to ephemeral connections, migration strategies, and ORM diversification. This section clarifies how to simplify those challenges with proven patterns for Prisma and Drizzle in Neon serverless environments.

Core Features & Use Cases

  • Prisma with Neon Connection: Configure Prisma to use a pooled connection for runtime workloads (via PgBouncer) and a direct connection for migrations.
  • Drizzle with Neon Serverless Driver: Use Drizzle ORM with Neon's serverless HTTP/WebSocket driver for edge environments.
  • Connection Pooling with PgBouncer: Neon provides built-in pooling; use the pooled endpoint for apps and the direct URL for migrations, with clear limits.

Quick Start

Configure Prisma and Drizzle to Neon using the pooled URL for runtime and the direct URL for migrations, then deploy to edge environments.

Frequently Asked Questions about neon-postgres

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Prisma with Neon Postgres for serverless environments?

To configure Prisma with Neon Postgres, use the pooled connection string via PgBouncer for runtime workloads and the direct connection string exclusively for running database migrations.

Can I use Drizzle ORM with Neon's serverless driver at the edge?

Yes, you can use Drizzle ORM with Neon's serverless HTTP or WebSocket driver to execute database queries directly within edge and serverless runtime environments.

Why do I need two connection strings for Neon Postgres?

Neon Postgres requires two connection strings because the pooled endpoint optimizes runtime application traffic via PgBouncer, while the direct endpoint bypasses pooling to execute migrations reliably.

What are the limitations of using PgBouncer connection pooling with Neon?

PgBouncer connection pooling in Neon limits certain features like prepared statements, making the direct connection endpoint necessary for executing complex migration scripts with Prisma or Drizzle.

Does Neon serverless Postgres work with both Prisma and Drizzle?

Yes, Neon serverless Postgres works with both Prisma and Drizzle, providing specific connection patterns for Prisma migrations and serverless HTTP driver configurations for Drizzle edge deployments.

When do I use a direct connection versus a pooled connection for Neon migrations?

Use a direct connection for Neon migrations to avoid PgBouncer limitations with migration scripts, and use the pooled connection for application runtime workloads to manage ephemeral serverless connections efficiently.