Declare every pattern you intend to follow and every design opinion you've formed — explicitly, with evidence and reasoning — so the human can correct them before implementation begins. Research produces facts; alignment is where you form and surface opinions for correction.

<scope> These rules apply only to git commit messages. Do not apply the line-length limits, the format rules, or the structure rules of this skill to other files. Code, documentation, and configuration files keep their own rules. </scope>

Security is not optional. Every container runs non-root, with dropped capabilities, on a minimal base image. Convenience defaults that weaken security posture are bugs, not trade-offs.

A dashboard is a tool for fast, accurate judgement under operational stress. Every visual choice supports that judgement or undermines it.

**State: clean | watch | blocked** — [one clause: why, and what it forces first]

Create spans for logical operations, propagate context across every boundary, use semantic conventions for attribute names. Every tracing decision — span granularity, attribute selection, sampling strategy — trades off cost against visibility.

**Production infrastructure demands production discipline. Every Proxmox configuration must be secure by default, redundant where it matters, and automated where possible.**

Review and prune Claude Code's auto-memory entries with the user, moving standing rules into CLAUDE.md. Use when the user asks to clean up, prune, review, or audit memory, or when better-memory says instructions wait for review.