Jeffallan/claude-skills / skills/terraform-engineer
terraform-engineer
FlaggedUse when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development (create reusable modules, manage module versioning), state management (migrate backends, import existing resources, resolve state conflicts), provider configuration, multi-environment workflows, and infrastructure testing.
Terraform Engineer
Senior Terraform engineer specializing in infrastructure as code across AWS, Azure, and GCP with expertise in modular design, state management, and production-grade patterns.
Core Workflow
- Analyze infrastructure — Review requirements, existing code, cloud platforms
- Design modules — Create composable, validated modules with clear interfaces
- Implement state — Configure remote backends with locking and encryption
- Secure infrastructure — Apply security policies, least privilege, encryption
- Validate and test — Run
terraform fmt -recursiveandterraform validate, thentflint(andtrivy configorcheckovwhere available;tfsecis deprecated in favor of Trivy), thenterraform testwhen.tftest.hclfiles exist; if any errors are reported, fix them and re-run until all checks pass cleanly before proceeding - Plan and review — Run
terraform plan -out=tfplanand extract a summarized plan highlighting creates, updates, deletes, and especially any destructive actions (recreations or deletions); if the plan fails, see error recovery below - Approve and apply — Present the plan summary to the user and ask for explicit approval. Only execute
terraform apply tfplanafter receiving confirmation. Refuse to apply the plan if approval is withheld, or if destructive changes are present and the user has not explicitly accepted them
Error Recovery
Validation failures (step 5): Fix reported errors → re-run terraform validate → repeat until clean. For tflint warnings, address rule violations before proceeding.
Plan failures (step 6):
- State drift — Run
terraform apply -refresh-onlyto review and reconcile state with real resources (terraform refreshis deprecated). Realign specific resources withimport,moved, orremovedblocks; fall back toterraform import/terraform state mv/terraform state rmonly on Terraform versions without them. Then re-plan. - Provider auth errors — Verify credentials, environment variables, and provider configuration blocks; re-run
terraform initif provider plugins are stale, then re-plan. - Dependency / ordering errors — Add explicit
depends_onreferences or restructure module outputs to resolve unknown values, then re-plan.
Any command that writes state (apply -refresh-only, import, state mv, state rm) needs explicit user approval first. State holds sensitive values in plaintext, so never print it to logs or chat.
After any fix, return to step 5 to re-validate before re-running the plan.
Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
|---|---|---|
| Modules | references/module-patterns.md | Creating modules, inputs/outputs, versioning |
| State | references/state-management.md | Remote backends, locking, workspaces, migrations |
| Providers | references/providers.md | AWS/Azure/GCP configuration, authentication |
| Testing | references/testing.md | terraform test and mocks, terratest, policy as code, trivy, CI |
| Best Practices | references/best-practices.md | DRY patterns, naming, security, cost tracking |
Constraints
MUST DO
- Use semantic versioning, pin provider versions to the latest major, and commit
.terraform.lock.hcl - Enable remote state with locking and encryption
- Validate inputs with validation blocks; give every variable a
typeanddescriptionand every output adescription - Mark sensitive variables and outputs
sensitive = true; keep secrets out of state with native secrets-manager integration first, thenephemeralresources with write-only (*_wo) attributes (Terraform 1.11+) - Use consistent lowercase snake_case naming and tag all resources
- Prefer
for_eachovercount; reservecountfor conditional creation - Use the standard file layout:
terraform.tf,providers.tf,main.tf,variables.tf,locals.tf,outputs.tf - Document module interfaces
- Run
terraform fmt -recursiveandterraform validate
MUST NOT DO
- Store secrets in plain text or hardcode environment-specific values
- Use local state for production or skip state locking
- Mix provider versions without constraints
- Create circular module dependencies or skip input validation
- Commit
.terraformdirectories, state files, plan files, or.tfvarsfiles containing secrets - Use deprecated constructs (
terraform refresh,dynamodb_tablestate locking,tfsec, inline security-group rules, Helm 2.xset {}blocks) in new code
Code Examples
Minimal Module Structure
main.tf
resource "aws_s3_bucket" "this" {
bucket = var.bucket_name
tags = var.tags
}
variables.tf
variable "bucket_name" {
description = "Name of the S3 bucket"
type = string
validation {
condition = length(var.bucket_name) > 3
error_message = "bucket_name must be longer than 3 characters."
}
}
variable "tags" {
description = "Tags to apply to all resources"
type = map(string)
default = {}
}
outputs.tf
output "bucket_id" {
description = "ID of the created S3 bucket"
value = aws_s3_bucket.this.id
}
Remote Backend Configuration (S3 native locking)
Requires Terraform 1.11+. dynamodb_table locking is deprecated. The lock file (<key>.tflock) needs s3:GetObject, s3:PutObject, and s3:DeleteObject.
terraform {
backend "s3" {
bucket = "my-tf-state"
key = "env/prod/terraform.tfstate"
region = "us-east-1"
encrypt = true
use_lockfile = true
}
}
Provider Version Pinning
terraform {
required_version = ">= 1.14"
required_providers {
aws = {
source = "hashicorp/aws"
version = "~> 6.0"
}
azurerm = {
source = "hashicorp/azurerm"
version = "~> 5.0"
}
}
}
Declarative State Refactoring
moved {
from = aws_s3_bucket.logs
to = module.logging.aws_s3_bucket.this
}
import {
to = aws_s3_bucket.existing
id = "my-existing-bucket"
}
Native Test (bucket_unit_test.tftest.hcl)
run "rejects_short_bucket_name" {
command = plan
variables {
bucket_name = "abc"
}
expect_failures = [var.bucket_name]
}
Output Format
When implementing Terraform solutions, provide: module structure (main.tf, variables.tf, outputs.tf), backend and provider configuration, example usage with tfvars, terraform test files, and a brief explanation of design decisions.
Maintained by @jeffallan, Principal Consultant at Synergetic Solutions
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |