postgres▌

Comprehensive guides and best practices for Neon Serverless Postgres, covering setup, connection methods, authentication, and platform APIs. \n \n Covers getting started, local development setup, connection method selection (TCP, HTTP, WebSocket), and driver installation for any language or framework \n Includes Neon-specific features: autoscaling, branching (instant copy-on-write clones), scale-to-zero, instant restore, and read replicas \n Provides CLI tooling ( neonctl ), TypeScript/Python SD

Passwordless PostgreSQL authentication on Azure with Microsoft Entra ID integration. \n \n Configures Entra ID authentication for Azure Database for PostgreSQL Flexible Server, eliminating password-based access in favor of token-based authentication \n Supports three access patterns: developer identities, managed identities for Azure-hosted applications, and group-based permissions via Azure AD groups \n Includes migration tooling to transition existing password-authenticated databases to Entra

Surfaces migration risks and validates migration work against known Oracle/PostgreSQL behavioral differences documented in the references/ folder.

Analyze a .NET solution, classify every project for Oracle→PostgreSQL migration eligibility, and write a structured plan that downstream agents and skills can parse.

Comprehensive performance optimization guide for Postgres, maintained by Supabase. Contains rules across 8 categories, prioritized by impact to guide automated query optimization and schema design.

Creates a compilable, empty xUnit test project with transaction management and seed data infrastructure for a single target project. Run once per project before writing tests.

Comprehensive performance optimization guide for Postgres, maintained by Supabase. Contains rules across 8 categories, prioritized by impact to guide automated query optimization and schema design.

Guide the user through diagnosing and fixing application-side query patterns that cause excessive data transfer (egress) from their Postgres database. Most high egress bills come from the application fetching more data than it uses.