postgresql-engineering

# PostgreSQL Engineering Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178. Use this parent skill as the active PostgreSQL engineering entrypoint. Keep implementation guidance here short; load the relevant reference module only when the task needs that depth. <!-- dual-compat-start --> ## Use When - Designing PostgreSQL-backed features, schemas, indexes, constraints, and access paths. - Reviewing SQL correctness, transaction boundaries, isolation assumptions, or extension usage. - Implementing functions, triggers, views, materialized views, or server-side routines. - Consolidating PostgreSQL-specific engineering advice before pairing with `database-design-engineering` or `database-reliability`. ## Do Not Use When - The task is unrelated to this parent skill or is better handled by a narrower active parent named in the workflow. - The request only needs a trivial answer and no reference module needs to be loaded. ## Required Inputs - Gather the concrete system, repository, environment, constraints, and deliverable before loading references. - Identify which absorbed reference file is needed; do not load every migrated reference by default. ## Workflow 1. Start with `database-design-engineering` for logical model, integrity, tenancy, and migration shape. 2. Load only the reference file matching the task: - `references/postgresql-fundamentals.md` for baseline PostgreSQL usage and core concepts. - `references/postgresql-patterns.md` for ...