Terraform Style Guide

This enforces HashiCorp's official Terraform style conventions so you stop arguing about formatting in code reviews. It handles the standard file organization (terraform.tf, providers.tf, main.tf, variables.tf, outputs.tf), ensures two-space indentation with aligned equals signs, and mandates descriptions on every variable and output. The guide prioritizes for_each over count, includes validation rules for variables, and covers version pinning strategies. Use it when generating new Terraform configurations or reviewing existing ones. It's opinionated about security practices and references a separate SECURITY.md, plus includes a pre-commit checklist covering fmt, validate, and basic hygiene checks.

skills.sh installs: 13.2K
GitHub stars: 924
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add hashicorp/agent-skills --skill terraform-style-guide --agent claude-code

Installs into .claude/skills of the current project.

Files

Terraform Style Guide

Generate and maintain Terraform code following HashiCorp's official style conventions and best practices.

Reference: HashiCorp Terraform Style Guide

Code Generation Strategy

When generating Terraform code:

Start with provider configuration and version constraints
Create data sources before dependent resources
Build resources in dependency order
Add outputs for key resource attributes
Use variables for all configurable values

File Organization

File	Purpose
`terraform.tf`	Terraform and provider version requirements
`providers.tf`	Provider configurations
`main.tf`	Primary resources and data sources
`variables.tf`	Input variable declarations (alphabetical)
`outputs.tf`	Output value declarations (alphabetical)
`locals.tf`	Local value declarations

Example Structure

# terraform.tf
terraform {
  required_version = ">= 1.14"

  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 6.0"
    }
  }
}

SKILL.md on GitHub