domains / families / devops / terraform

terraform

combined

Diagnoses and designs safe Terraform releases, provisioners (remote-exec/local-exec/file, cloud-init, Compose, Caddy), multi-environment isolation, and fresh-host bootstrap. Use when writing or reviewing plan/apply wrappers or provisioners; when staging/production config may differ; when a rollout can mutate a shared gateway; or debugging drift, TLS, container restarts, DNS duplication, or snapshot contamination. Terraform infrastructure as code best practices

When to use

• Creating new Terraform or OpenTofu configurations or modules
• Setting up testing infrastructure for IaC code
• Deciding between testing approaches (validate, plan, frameworks)
• Structuring multi-environment deployments
• Implementing CI/CD for infrastructure-as-code
• Reviewing or refactoring existing Terraform/OpenTofu projects
• Choosing between module patterns or state management approaches
• Basic Terraform/OpenTofu syntax questions (Claude knows this)

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies address different Terraform tasks. The daymade copy is a release-safety and provisioner-troubleshooting procedure (canonical release entry, environment parity, saved-plan binding, provisioner side effects, and incident-derived symptom patterns). The sickn33 copy is a general IaC best-practices guide (count vs for_each, module patterns, CI/CD, and security scanning). They overlap only in the broad domain of Terraform, and neither contains the other's material steps, so crowning one would hide a real alternative.