terraform-style-guide

Generate Terraform configurations conforming to HashiCorp's style guide.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/eggboy/skills --skill terraform-style-guide-eggboy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terraform-style-guide
Source: https://github.com/eggboy/skills/tree/main/terraform-style-guide
Command: npx skills add https://github.com/eggboy/skills --skill terraform-style-guide-eggboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates Terraform configurations that adhere to HashiCorp's official style conventions and best practices, improving readability, consistency, and maintainability across teams.

Core Features & Use Cases

  • Enforce provider configuration, version constraints, and resource ordering.
  • Promote consistent file organization and naming conventions for Terraform projects.
  • Use when writing, reviewing, or generating Terraform configurations to ensure security and compliance.

Quick Start

Use this skill to generate a compliant Terraform configuration structure for a new project.

Frequently Asked Questions about terraform-style-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Terraform code that follows HashiCorp style conventions?

You can generate Terraform code conforming to HashiCorp style by automating provider blocks, resources, variables, and outputs creation in dependency order. This ensures your Terraform projects maintain formatting, naming, and security best practices.

What are the best practices for organizing Terraform project file structure and naming conventions?

Terraform best practices for project organization involve enforcing consistent file structure, naming conventions, and resource ordering. This includes configuring provider blocks, version constraints, and outputs in a standardized dependency order for maintainability.

Does this approach to writing Terraform configurations work for projects of varying sizes?

Yes, applying this style guide automation to writing Terraform configurations works for projects of varying sizes. It systematically structures provider blocks, resources, and variables to ensure consistent infrastructure-as-code regardless of project scale.

How do I enforce security and version pinning requirements in my HCL configurations?

To enforce security and version pinning in HCL configurations, generate Terraform code that strictly satisfies HashiCorp style guide requirements. This automatically handles version constraints and security best practices across provider and resource blocks.

Why does my Terraform code lack consistency when reviewing infrastructure-as-code across teams?

Terraform code lacks consistency across teams when it does not adhere to standard style conventions. Automating the generation of configurations that conform to HashiCorp's style guide improves readability, maintainability, and compliance during code reviews.