postgresql-engineering
/postgresql-engineering
Use when designing, implementing, administering, tuning, backing up, restoring, monitoring, or troubleshooting PostgreSQL schemas and production systems; use database-reliability for datastore-independent SLO and recovery policy.
- Author
- peterbamuhigire ↗
- Repository
- chwezi-dev-engine ↗
- Licence
- MIT
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 12
- Scripts
- 0
- HTML comments
- 2
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
Use when designing, implementing, administering, tuning, backing up, restoring, monitoring, or troubleshooting PostgreSQL schemas and production systems; use database-reliability for datastore-independent SLO and recovery policy.
Original author description
Use when designing, implementing, administering, tuning, backing up, restoring, monitoring, or troubleshooting PostgreSQL schemas and production systems; use database-reliability for datastore-independent SLO and recovery policy.
How it works
- Use When
- Do Not Use When
- Required Inputs
- Workflow
- Quality Standards
- Anti-Patterns
- Outputs
- References
- Evidence Produced
- Inputs
SKILL.md preview
--- name: postgresql-engineering description: Use when designing, implementing, administering, tuning, backing up, restoring, monitoring, or troubleshooting PostgreSQL schemas and production systems; use database-reliability for datastore-independent SLO and recovery policy. metadata: portable: true compatible_with: - claude-code - codex --- # 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 schema and application patterns. - `references/postgresql-advanced-sql.md` for advanced query design. - `references/postgresql-server-programming.md` for functions, triggers, and server-side behaviour. 3. Administration, performance incidents, tuning, backups, and production operations also route here (the retired `postgresql-operations` skill is an inactive alias of this skill). 4. Pair with `ai-rag-patterns` only when pgvector or AI platform concerns are central. ## Quality Standards - Preserve data integrity with constraints, types, and transaction design before relying on application checks. - Make query plans reviewable: expected indexes, cardinality assumptions, and failure cases must be explicit. - Treat migrations as reversible operational changes with lock, runtime, and rollback impact stated. ## Anti-Patterns - Treating absorbed reference files as active skills or separate routing entrypoints. - Loading every migrated child reference instead of the one that matches the task. - Producing generic advice without constraints, evidence, or next verification steps. ## Outputs - PostgreSQL schema, SQL, migration, or review notes with integrity and performance evidence. - Reference files loaded and companion skills used. ## References - Load the retained [PostgreSQL operations workflow](../postgresql-operations/ALIAS.md) for backup, restore, vacuum, replication, production tuning, monitoring, and incidents. - Load only the references/<old-skill>.md files named in the workflow when their depth is required. ## Evidence Produced | Category | Artifact | Format | Example | | --- | --- | --- | --- | | Data safety | PostgreSQL schema and operations evidence pack | DDL, query plans, and runbook | constraints, migration, vacuum/replication evidence, restore result, and rollback | <!-- dual-compat-end --> ## Inputs | Input | Required | Purpose | |---|---|---| | PostgreSQL version and schema | yes | Select valid features | | Query plans and cardinalities | yes | Design indexes | | Migration and availability constraints | yes | Plan safe change | ## Capability contract Review SQL and propose DDL by default. Execute migrations, extensions, routines, or data changes only with authorised scope and rollback. ## Degraded mode If EXPLAIN ANALYZE or statistics are unavailable, provide read-only hypotheses and validation SQL; do not claim measured improvement. ## Decision rules | Condition | Action | |---|---| | Planner estimate is materially wrong | Refresh or improve statistics | | Index build may block writes | Use a compatible concurrent path | | Constraint encodes business truth | Enforce it in the database | ## Domain Anti-Patterns - Running EXPLAIN ANALYZE on unsafe writes. Fix: use a rollback-safe test. - Adding extensions without trust review. Fix: verify source and privileges. - Indexing without workload evidence. Fix: compare read and write cost. - Hiding null semantics in application code. Fix: define them in schema. - Combining expand and contract in one release. Fix: stage compatibility.
Files in this package (12)
- SKILL.md 5 KB
- references/postgresql-advanced-sql.md 14 KB
- references/postgresql-fundamentals.md 13 KB
- references/postgresql-patterns.md 17 KB
- references/postgresql-server-programming.md 6 KB
- references/postgresql-patterns/references/jsonb-and-fts.md 3 KB
- references/postgresql-patterns/references/mysql-to-postgres.md 3 KB
- references/postgresql-patterns/references/operations.md 4 KB
- references/postgresql-patterns/references/pgbouncer.md 3 KB
- references/postgresql-patterns/references/pgvector.md 4 KB
- references/postgresql-patterns/references/supabase-rls.md 3 KB
- references/postgresql-server-programming/references/skill-deep-dive.md 11 KB
Versions
The database has no other skills named postgresql-engineering.
Database snapshot: 13.11.2026 · package version 9508d5974347 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100mysql-engineering
Use when designing, implementing, administering, tuning, backing up, restoring, monitoring, or troubleshooting MySQL schemas and production systems; use database-reliability for datastore-independent SLO and recovery policy. - 100postgresql
Administer PostgreSQL databases. Configure replication, backups, and performance tuning. Use when managing PostgreSQL deployments. - 95database-expert
Advanced database design and administration for PostgreSQL, MongoDB, and Redis. Use when designing schemas, optimizing queries, managing database performance, or implementing data patterns. - 100devops-databases
Use when operating (not designing) databases - PostgreSQL installation and tuning (postgresql.conf, pg_hba.conf, roles), PgBouncer pooling, backups and point-in-time recovery (pg_dump, pg_basebackup, pgBackRest, restore tests), streaming and logical replication, Patroni high… - 100agent-database-expert
Specialist subagent: Expert database architect and engineer for PostgreSQL, MongoDB, Redis, and all major databases. Use when designing schemas, optimizing queries, planning migrations, implementing caching, or troubleshooting database performance. - 100postgresql-devsec
Administer PostgreSQL databases. Configure replication, backups, and performance tuning. Use when managing PostgreSQL deployments.