neon-vercel-postgres▌
jezweb/claude-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Serverless Postgres setup for edge functions with connection pooling, branching, and ORM integration.
- ›Supports Neon Direct (multi-cloud, Cloudflare Workers) and Vercel Postgres (zero-config on Vercel); both use HTTP/WebSocket protocols instead of TCP for edge compatibility
- ›Requires pooled connection strings ( -pooler. in hostname) for serverless; non-pooled connections exhaust quickly in high-concurrency environments
- ›Template tag syntax ( sql`...` ) prevents SQL injection; string con
Neon & Vercel Serverless Postgres
Status: Production Ready
Last Updated: 2026-01-21
Dependencies: None
Latest Versions: @neondatabase/[email protected], @vercel/[email protected], [email protected], [email protected], [email protected]
Quick Start (5 Minutes)
1. Choose Your Platform
Option A: Neon Direct (multi-cloud, Cloudflare Workers, any serverless)
npm install @neondatabase/serverless
Option B: Vercel Postgres (Vercel-only, zero-config on Vercel)
npm install @vercel/postgres
Note: Both use the same Neon backend. Vercel Postgres is Neon with Vercel-specific environment setup.
Why this matters:
- Neon direct gives you multi-cloud flexibility and access to branching API
- Vercel Postgres gives you zero-config on Vercel with automatic environment variables
- Both are HTTP-based (no TCP), perfect for serverless/edge environments
2. Get Your Connection String
For Neon Direct:
# Sign up at https://neon.tech
# Create a project → Get connection string
# Format: postgresql://user:[email protected]/dbname?sslmode=require
For Vercel Postgres:
# In your Vercel project
vercel postgres create
vercel env pull .env.local # Automatically creates POSTGRES_URL and other vars
CRITICAL:
- Use pooled connection string for serverless (ends with
-pooler.region.aws.neon.tech) - Non-pooled connections will exhaust quickly in serverless environments
- Always include
?sslmode=requireparameter
3. Query Your Database
Neon Direct (Cloudflare Workers, Vercel Edge, Node.js):
import { neon } from '@neondatabase/serverless';
const sql = neon(process.env.DATABASE_URL!);
// Simple query
const users = await sql`SELECT * FROM users WHERE id = ${userId}`;
// Transactions
const result = await sql.transaction([
sql`INSERT INTO users (name) VALUES (${name})`,
sql`SELECT * FROM users WHERE name = ${name}`
]);
Vercel Postgres (Next.js Server Actions, API Routes):
import { sql } from '@vercel/postgres';
// Simple query
const { rows } = await sql`SELECT * FROM users WHERE id = ${userId}`;
// Transactions
const client = await sql.connect();
try {
await client.sql`BEGIN`;
await client.sql`INSERT INTO users (name) VALUES (${name})`;
await client.sql`COMMIT`;
} finally {
client.release();
}
CRITICAL:
- Use template tag syntax (
sql`...`) for automatic SQL injection protection - Never concatenate strings:
sql('SELECT * FROM users WHERE id = ' + id)❌ - Template tags automatically escape values and prevent SQL injection
The 7-Step Setup Process
Step 1: Install Package
Choose based on your deployment platform:
Neon Direct (Cloudflare Workers, multi-cloud, direct Neon access):
npm install @neondatabase/serverless
Vercel Postgres (Vercel-specific, zero-config):
npm install @vercel/postgres
With ORM:
# Drizzle ORM (recommended for edge compatibility)
npm install [email protected] @neondatabase/[email protected]
npm install -D [email protected]
# Prisma (Node.js only)
npm install prisma @prisma/client @prisma/adapter-neon @neondatabase/serverless
Key Points:
- Both packages use HTTP/WebSocket (no TCP required)
- Edge-compatible (works in Cloudflare Workers, Vercel Edge Runtime)
- Connection pooling is built-in when using pooled connection strings
- No need for separate connection pool libraries
Step 2: Create Neon Database
Option A: Neon Dashboard
- Sign up at https://neon.tech
- Create a new project
- Copy the pooled connection string (important!)
- Format:
postgresql://user:[email protected]/db?sslmode=require
Option B: Vercel Dashboard
- Go to your Vercel project → Storage → Create Database → Postgres
- Vercel automatically creates a Neon database
- Run
vercel env pullto get environment variables locally
Option C: Neon CLI ([email protected])
# Install CLI
npm install -g [email protected]
# Authenticate
neonctl auth
# Create project and get connection string
neonctl projects create --name my-app
neonctl connection-string main
CRITICAL:
- Always use the pooled connection string (ends with
-pooler.region.aws.neon.tech) - Non-pooled connections are for direct connections (not serverless)
- Include
?sslmode=requirein connection string
Step 3: Configure Environment Variables
For Neon Direct:
# .env or .env.local
DATABASE_URL="postgresql://user:[email protected]/neondb?sslmode=require"
For Vercel Postgres:
# Automatically created by `vercel env pull`
POSTGRES_URL="..." # Pooled connection (use this for queries)
POSTGRES_PRISMA_URL="..." # For Prisma migrations
POSTGRES_URL_NON_POOLING="..." # Direct connection (avoid in serverless)
POSTGRES_USER="..."
POSTGRES_HOST="..."
POSTGRES_PASSWORD="..."
POSTGRES_DATABASE="..."
For Cloudflare Workers (wrangler.jsonc):
{
"vars": {
"DATABASE_URL": "postgresql://user:[email protected]/neondb?sslmode=require"
}
}
Key Points:
- Use
POSTGRES_URL(pooled) for queries - Use
POSTGRES_PRISMA_URLfor Prisma migrations - Never use
POSTGRES_URL_NON_POOLINGin serverless functions - Store secrets securely (Vercel env, Cloudflare secrets, etc.)
Step 4: Create Database Schema
Option A: Raw SQL
// scripts/migrate.ts
import { neon } from '@neondatabase/serverless';
const sql = neon(process.env.DATABASE_URL!);
await sql`
CREATE TABLE IF NOT EXISTS users (
id SERIAL PRIMARY KEY,
name TEXT NOT NULL,
email TEXT UNIQUE NOT NULL,
created_at TIMESTAMP DEFAULT NOW()
)
`;
Option B: Drizzle ORM (recommended)
// db/schema.ts
import { pgTable, serial, text, timestamp } from 'drizzle-orm/pg-core';
export const users = pgTable('users', {
id: serial('id').primaryKey(),
name: text('name').notNull(),
email: text('email').notNull().unique(),
createdAt: timestamp('created_at').defaultNow()
});
// db/index.ts
import { drizzle } from 'drizzle-orm/neon-http';
import { neon } from '@neondatabase/serverless';
import * as schema from './schema';
const sql = neon(process.env.DATABASE_URL!How to use neon-vercel-postgres on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add neon-vercel-postgres
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches neon-vercel-postgres from GitHub repository jezweb/claude-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate neon-vercel-postgres. Access the skill through slash commands (e.g., /neon-vercel-postgres) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.4★★★★★68 reviews- ★★★★★Olivia Khan· Dec 28, 2024
Solid pick for teams standardizing on skills: neon-vercel-postgres is focused, and the summary matches what you get after install.
- ★★★★★Camila Verma· Dec 24, 2024
Keeps context tight: neon-vercel-postgres is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Mateo Harris· Dec 12, 2024
Registry listing for neon-vercel-postgres matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Omar Abbas· Dec 8, 2024
We added neon-vercel-postgres from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Mateo Thompson· Dec 4, 2024
neon-vercel-postgres has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Soo Flores· Nov 27, 2024
neon-vercel-postgres is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Omar Choi· Nov 27, 2024
Solid pick for teams standardizing on skills: neon-vercel-postgres is focused, and the summary matches what you get after install.
- ★★★★★Jin Chen· Nov 23, 2024
neon-vercel-postgres fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Noah Mehta· Nov 19, 2024
We added neon-vercel-postgres from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Sakshi Patil· Nov 3, 2024
neon-vercel-postgres is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 68