Developers struggle with serverless database connection management and ORM configuration. This skill provides proven patterns for Neon Postgres with Prisma and Drizzle integration.
スキルZIPをダウンロード
Claudeでアップロード
設定 → 機能 → スキル → スキルをアップロードへ移動
オンにして利用開始
テストする
「neon-postgres」を使用しています。 Configure Prisma for Neon Postgres
期待される結果:
Prisma datasource configured with dual connection strings: DATABASE_URL for pooled runtime connections (PgBouncer) and DIRECT_URL for direct migration operations. Schema includes proper provider and url settings.
「neon-postgres」を使用しています。 Set up Drizzle with Neon serverless driver
期待される結果:
Drizzle instance initialized with neon-serverless driver, enabling WebSocket-based sessions for transactions. HTTP driver available for simple queries in edge environments.
セキュリティ監査
安全Static analysis flagged 4 patterns that are all false positives. The skill contains documentation-only content with no executable code. Environment variable references are configuration examples, not actual env access. Cryptographic algorithm warnings are pattern-matching errors on unrelated text.
品質スコア
作れるもの
Full-Stack Developer Setting Up New Project
Configure database connections for a new Next.js project using Prisma with Neon Postgres, including proper separation of pooled and direct connections.
Edge Application Database Integration
Implement Drizzle ORM with Neon serverless driver for edge runtime compatibility in serverless functions.
Database Migration Workflow
Set up safe migration workflows using direct connections while maintaining pooled connections for application runtime.
これらのプロンプトを試す
Help me configure a Neon Postgres connection string for my application. I need to understand the difference between pooled and direct connections.
Generate a Prisma schema configuration for Neon Postgres with proper datasource setup for both DATABASE_URL and DIRECT_URL environment variables.
Show me how to configure Drizzle ORM with the Neon serverless driver for use in Vercel Edge Functions, including transaction support.
Analyze my application connection patterns and recommend optimal PgBouncer pooling settings for Neon Postgres given my expected concurrent user load.
ベストプラクティス
- Always use pooled connections for application runtime and direct connections for migrations
- Reserve 7 connections for Neon superuser operations when calculating pool limits
- Use database branching for isolated development and testing environments
回避
- Using direct connection strings for application runtime connections
- Exceeding connection pool limits without proper error handling
- Running migrations against pooled connections instead of direct connections