Production-grade platform engineering handbook — Kubernetes, Terraform, Flux CD, GitHub Actions, AWS, and more.
67
84%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Mistakes made, wrong assumptions, and root causes. Captured automatically via PostToolUse hook or logged manually.
Format: ERR-YYYYMMDD-NNN
Lifecycle: pending → resolved → promoted
Status: example
Context: Applying a Terraform plan that replaced an RDS instance
Content: Assumed that changing db_subnet_group_name was a non-destructive update. It is a replacement trigger. The plan showed forces replacement but the flag was missed during review.
Action: Resolved — added a lifecycle { prevent_destroy = true } block. Promoted to references/terraform.md: "Always scan plan output for forces replacement before applying to stateful resources."
.claude-plugin
.github
commands
docs
examples
agent-self-improve
argocd
awesome-docs
aws
cloudfront
functions
lambda-edge
functions
azure
compliance
conventional-commits
datadog
llm-observability
demo
documentation
dora
dynatrace
fluxcd
github-actions
composite-actions
configure-cloud
db-migrate
docker-build-push
k8s-deploy
notify-slack
pr-comment
release-tag
security-scan
setup-env
setup-terraform
terraform-plan
helm
web-service
templates
kubernetes
kyverno
mcp
observability
openshift
pr-review
ownership
runtime-security
supply-chain
terraform
references
scripts
skills
platform-skills
tests