What problem does it solve? Writing Terraform without consistent conventions leads to unpinned providers, unstable resource addressing, leaked secrets, and failed applies. This Skill provides a structured set of HCL authoring standards covering project layout, resource patterns, module design, and pre-commit validation. ## Core Features & Use Cases - Project Setup Standards: Defines file organization (terraform.tf, providers.tf, variables.tf, outputs.tf) and enforces version pinning for both the Terraform CLI and providers. - Resource Authoring Rules: Covers naming conventions, variable validation blocks, for_each over count for stable addressing, and security defaults like encryption at rest and sensitive outputs. - Module Development: Specifies standard module layout, input validation, output composition patterns, and a pre-commit checklist using terraform fmt, validate, tflint, and tfsec. - Use Case: When refactoring a VPC module, apply the composition pattern to consume outputs like vpc_id and private_subnet_ids from one module in another, then run the pre-commit checklist before pushing. ## Quick Start Use the terraform skill to review my main.tf and variables.tf for naming, validation, and security issues before I commit.