skills.rest
kumewata
kumewataCOMMUNITY
Explore all skills by this author →
GitHub

terraform-style-guide

Enforces HashiCorp Terraform style conventions across configuration files and naming rules.

Updated Jan 16, 2026
Search Tags:#terraform#best-practices#infrastructure-as-code#naming-conventions#style-guide#code-organization
One-click install
npx skills add https://github.com/kumewata/dotfiles --skill terraform-style-guide-kumewata
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: terraform-style-guide
Source: https://github.com/kumewata/dotfiles/tree/main/config/agents/skills/terraform-style-guide
Command: npx skills add https://github.com/kumewata/dotfiles --skill terraform-style-guide-kumewata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Terraform projects often suffer from inconsistent style, structure, and naming, making maintenance and collaboration difficult across teams.

Core Features & Use Cases

  • Provides a standardized file organization for Terraform configurations (terraform.tf, variables.tf, outputs.tf, etc.).
  • Enforces naming conventions, variable and output descriptions, and consistent provider configuration.
  • Guides secure and maintainable infrastructure code with best practices and example structures.

Quick Start

Create a new Terraform project and apply the style-guide's file layout and naming rules to ensure consistency across the repository.

Frequently Asked Questions about terraform-style-guide

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

FAQPage Schema
What are the best practices for Terraform file organization and structure?▼

Terraform style conventions enforce consistent file organization, variable and output descriptions, and naming rules across configurations to make infrastructure-as-code maintenance and collaboration easier.

How do I enforce naming conventions in Terraform configurations?▼

You can enforce Terraform naming conventions by applying a style guide during the authoring, reviewing, or generating phases to codify variable, output, and resource naming rules consistently across projects.

What's the best way to standardize provider configuration and version pinning in Terraform?▼

The best way to standardize provider configuration and version pinning is to codify these rules in a style guide, ensuring secure and maintainable infrastructure code with consistent provider setups.

Does this Terraform style guide apply when generating new infrastructure-as-code projects?▼

Yes, you apply the style guide during authoring and generation to ensure new Terraform projects start with a standardized file layout, naming rules, and security best practices from the beginning.

Why does my Terraform codebase suffer from inconsistent structure and naming?▼

Terraform codebases suffer from inconsistent style when teams lack a centralized style guide, making collaboration difficult and leading to unstructured file layouts and non-standardized variable naming.

Related Skills

Explore More Software Engineering Skills→
jholhewresjholhewres
3

terraform

Manage cloud infrastructure as code with Terraform CLI.

Community
Advanced
mysticaltechmysticaltech
3.9k

test-changes

Run terraform fmt, validate, and plan against a test environment.

Community
Intermediate
alxayoalxayo
17

checkov-security-scan

Detect security misconfigurations and compliance violations in Infrastructure as Code.

Community
Advanced
rezosndrezosnd

excel-generator

Generate styled Excel workbooks with formulas, charts, and data validation.

Community
Intermediate