orlandinhom

terraform-best-practices

orlandinhom/claude-skills/skills/terraform-best-practices/SKILL.md

Writes and organizes Terraform under four non-negotiable structural rules: everything in first-party modules designed for reuse, environments separated as folders (never workspaces), zero community modules, and provider versions always looked up in the registry before being written. Use whenever the user says "write the terraform", "create the infrastructure as code", "provision this with terraform", "set up the terraform project structure", "organize this terraform", "review my terraform", "create the module", "add a new environment", or points at a repository with .tf files wanting to create or change infrastructure. Trigger it also when the task is just creating or editing a single .tf file — the wrong structure is born precisely out of "just a quick main.tf" — and when the request mentions a community module (terraform-aws-modules, Azure/, terraform-google-modules), because the right move there is to write the equivalent first-party module. Applies to any cloud or provider. Do NOT trigger for: plain Kubernetes/Helm manifests (no Terraform involved), Pulumi, CloudFormation or CDK, and debugging cloud API errors (permissions, quota, service limits) that are not a matter of code structure.