What problem does it solve? Working with PostgreSQL—especially Azure Database for PostgreSQL—involves platform-specific constraints (no superuser, no ALTER SYSTEM, allowlisted extensions) that generic advice gets wrong, leading to failed commands, broken auth, and irreversible operations. ## Core Features & Use Cases - Routing to specialized references: Keyword-triggered routing to 20+ reference guides covering indexing, JSONB, partitioning, RLS, full-text search, replication, connection pooling, and query performance. - Azure-specific guardrails: Enforces managed-service constraints (no ALTER SYSTEM, no file paths, no OS commands) and routes to Azure equivalents like az CLI, parameter APIs, PITR, and Entra ID auth. - Safety policies: Requires confirmation before destructive DDL or destructive az CLI commands, detects Azure flavor (Flexible Server vs HorizonDB), and applies anti-hallucination rules. - Use Case: A developer asks how to add pgvector to an Azure Flexible Server; the skill detects the Azure context, walks through the azure.extensions allowlist append workflow, and runs CREATE EXTENSION vector with the correct binary name. ## Quick Start Ask how to set up row-level security for a multi-tenant PostgreSQL database, or how to configure Entra ID authentication on Azure Database for PostgreSQL.