Menu
Kubernetes and operator design rules for PACMAN deployment topology and member behavior.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Require a concrete change explanation and explicit user approval before modifying a repository, then implement and verify the approved scope. Use whenever Codex is asked to create, edit, delete, generate, format, refactor, fix, upgrade, or otherwise mutate repository files, dependencies, configuration, tests, documentation, build artifacts, or version-control state.
Repository layout for the pacman Go PostgreSQL HA cluster manager.
Use when inspecting GitHub Actions, CI failures, failed Go tests, workflow logs, or build/lint/test errors. Avoid reading full logs; summarize failed jobs and inspect only relevant snippets.
Maintain PACMAN-native and Patroni-compatible API contracts.
PACMAN domain rules for cluster state transitions and operation history.
Rules for PACMAN control-plane quorum, leases, epochs, fencing, and split-brain prevention.
| name | k8s-deployment |
| description | Kubernetes and operator design rules for PACMAN deployment topology and member behavior. |
Use when discussing or editing Kubernetes/operator design, manifests, topology, or member identity behavior.
Primary references:
docs/ARCHITECTURE_K8S.md: Kubernetes architecture.deploy/**: current deployment/lab assets.internal/cluster/spec.go: cluster spec and member expectations.internal/controlplane, internal/agent: behavior that deployment must
preserve.Rules: