terraform-style-guide

Generate and maintain Terraform code following HashiCorp's official style conventions. Generate and maintain Terraform code following HashiCorp's official style conventions and best practices. Reference: HashiCorp Terraform Style Guide When generating Terraform code: Arguments precede blocks, with meta-arguments first: Every variable must include type and description : Every output must include description : Refer to SECURITY.md. It includes guidance on encrypting resources, preventing sensitive data in state, and secure configurations. Use the latest major version of each provider and the latest minor version of Terraform, unless otherwise constrained by a dependency lock file or by other modules used by the configuration. Version constraint operators: Never commit: Always commit: Run before committing: Additional tools: Based on: HashiCorp Terraform Style Guide - Enforces two-space indentation, lowercase underscore naming, and standard file organization across terraform.tf , providers.tf , main.tf , variables.tf , outputs.tf , and locals.tf - Requires type and description on all variables and outputs, with validation rules and sensitive flag support for credentials - Prioritizes for_each over count for dynamic resources, applies security hardening (encryption, private networking, least privilege), and prevents hardcoded secrets - Includes version pinning strategies, provider...