What problem does it solve? Setting up and operating a serverless Postgres database involves many decisions—pooled versus direct connections, driver selection per runtime, branching, migrations, autoscaling, and cost controls—and mistakes like running migrations over a pooled connection cause confusing failures. This Skill provides structured guidance for every stage of working with Neon Postgres. ## Core Features & Use Cases - Setup and Connection Guidance: Walks through selecting projects, retrieving connection strings via CLI or MCP, and choosing the right driver (Drizzle, node-postgres, @neondatabase/serverless) for Vercel, Cloudflare, or edge runtimes. - Pooled vs Direct Connection Rules: Explains when to use the -pooler hostname versus the direct URL, preventing errors like failed migrations, broken SET session state, and read-only transaction issues. - Platform Feature Coverage: Documents branching, schema migrations, autoscaling, scale-to-zero, instant restore, read replicas, connection pooling, IP allow lists, and logical replication. - Use Case: You are deploying a serverless app on Vercel with Drizzle ORM. Use this Skill to get the correct pooled DATABASE_URL for queries, the direct URL for Drizzle Kit migrations, and a branch of production to test the migration safely first. ## Quick Start Ask the AI to help you connect your application to a Neon Postgres database with the correct driver and connection string for your deployment platform.