neon-vercel-postgres

Neon Postgres with Vercel integration for serverless databases.

Installation

npx claude-plugins install @jezweb/claude-skills/neon-vercel-postgres

Contents

Folders: assets, references, scripts, templates

Files: README.md, SKILL.md

Documentation

Status: ✅ Production Ready Package Versions: @neondatabase/[email protected], @vercel/[email protected] Last Updated: 2025-10-29

What This Skill Does

This skill provides comprehensive patterns for integrating Neon serverless Postgres and Vercel Postgres (built on Neon) into serverless and edge environments. It covers both direct Neon usage (multi-cloud, Cloudflare Workers) and Vercel-specific setup (zero-config on Vercel).

Key Features

• ✅ HTTP/WebSocket-based Postgres (no TCP required - works in edge runtimes)
• ✅ Connection pooling patterns for serverless environments
• ✅ Database branching workflows (git-like database branches for preview environments)
• ✅ Drizzle ORM and Prisma integration
• ✅ Transaction handling patterns
• ✅ SQL injection prevention (template tag syntax)
• ✅ Point-in-time restore (PITR) and backup strategies
• ✅ Migration workflows across multiple ORMs

Auto-Trigger Keywords

Claude should automatically propose this skill when encountering:

Package Names

• @neondatabase/serverless
• @vercel/postgres
• neonctl
• drizzle-orm (with Postgres)
• @prisma/adapter-neon

Technologies

• neon postgres
• vercel postgres
• serverless postgres
• postgres edge
• postgres cloudflare
• postgres vercel edge
• http postgres
• websocket postgres
• edge database
• serverless sql

Use Cases

• neon branching
• database branches
• pooled connection
• postgres migrations
• point in time restore
• preview environments database
• serverless database setup
• edge postgres

Error Messages & Problems

• “connection pool exhausted”
• “too many connections for role”
• “TCP connections are not supported in serverless”
• “connection requires SSL”
• “sslmode required”
• “PrismaClient is unable to be run in the browser”
• “Query timeout”
• “transaction timeout”
• “database does not exist” (after branch deletion)
• SQL injection concerns in serverless
• Connection string format confusion

Frameworks & Platforms

• cloudflare workers postgres
• vercel edge postgres
• next.js postgres
• vite postgres
• server actions postgres
• drizzle neon
• prisma neon

When to Use This Skill

✅ Use This Skill When:

1. Setting up Neon Postgres for Cloudflare Workers, Vercel Edge Functions, or any serverless environment
2. Configuring Vercel Postgres for Next.js applications with zero-config setup
3. Implementing database branching for preview deployments (PR-specific database branches)
4. Migrating from D1/SQLite to Postgres or from traditional Postgres to serverless Postgres
5. Integrating Drizzle ORM or Prisma with Neon/Vercel Postgres
6. Debugging connection pool errors, transaction timeouts, or SSL configuration issues
7. Setting up point-in-time restore (PITR) or database backup strategies
8. Encountering errors like:
   • connection pool exhausted
   • TCP connections not supported
   • sslmode required
   • PrismaClient is unable to be run in the browser
   • Connection leaks or memory issues
9. Need git-like workflows for databases (create, test, merge, delete branches)
10. Want HTTP-based Postgres that works in edge runtimes without TCP

❌ Don’t Use This Skill For:

• SQLite databases (use cloudflare-d1 skill instead)
• Traditional Postgres with TCP connections (not serverless-optimized)
• MySQL or other SQL databases
• NoSQL databases (MongoDB, DynamoDB, etc.)
• Read-only databases or data warehouses

Errors Prevented (15 Total)

This skill prevents 15 documented errors:

1. Connection pool exhausted - Using non-pooled connection strings in serverless
2. TCP connections not supported - Using traditional pg client in edge runtime
3. SQL injection - String concatenation instead of template tags
4. Missing SSL mode - Connection string without ?sslmode=require
5. Connection leak - Forgetting client.release() in manual transactions
6. Wrong environment variable - Using DATABASE_URL vs POSTGRES_URL confusion
7. Transaction timeout in edge functions - Long-running transactions
8. Prisma in Cloudflare Workers - Prisma requires Node.js runtime
9. Branch API authentication error - Missing NEON_API_KEY
10. Stale connection after branch delete - Application using deleted branch connection string
11. Query timeout on cold start - Neon auto-suspend wake time
12. Drizzle schema mismatch - Database schema changed but types not regenerated
13. Migration conflicts across branches - Multiple branches with different migration histories
14. PITR timestamp out of range - Restoring from outside retention window
15. Wrong Prisma adapter - Not using @prisma/adapter-neon for serverless

Sources: GitHub issues, official docs, Stack Overflow, production debugging

Token Efficiency

Estimated Token Savings: ~65% vs manual setup Time to Implement: 5-10 minutes (vs 30-60 minutes without skill)

Without This Ski

Source

View on GitHub