terraform-coder

Enforce Terraform module structure, variable typing, and validation standards.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MunusCaritatis/dbtools --skill terraform-coder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terraform-coder
Source: https://github.com/MunusCaritatis/dbtools/tree/main/.skills/terraform-coder
Command: npx skills add https://github.com/MunusCaritatis/dbtools --skill terraform-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Terraform development teams struggle to maintain consistent coding standards, module organization, and robust reviews across multiple infrastructure projects.

Core Features & Use Cases

  • Enforces standard module layout (main.tf, variables.tf, outputs.tf, versions.tf, README.md)
  • Enforces variable typing, validation, and descriptive outputs
  • Provides templates and guardrails for provider configuration, tagging, and security practices
  • Supports scaffolding new modules and auditing existing ones for best practices
  • Use cases: starting new modules, refactoring, or code reviews across environments

Quick Start

Scaffold or refactor a Terraform module to conform with the project's coding standards.

Frequently Asked Questions about terraform-coder

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

FAQPage Schema
How do I enforce consistent Terraform coding standards across multiple environments?

You can enforce Terraform coding standards by automating module structure validation, enforcing typed inputs and outputs, and applying tagging and security best practices across your infrastructure-as-code projects.

What is the standard layout for a Terraform module?

A standard Terraform module layout includes main.tf, variables.tf, outputs.tf, versions.tf, and README.md files to ensure consistent organization, typed inputs, and proper documentation.

How do I refactor existing Terraform modules to follow best practices?

Refactor existing Terraform modules by auditing them against coding standards, updating variable typing and validation, standardizing provider configuration, and aligning the file structure with the standard layout.

Can I use automated linting and validation for Terraform variable inputs and outputs?

Yes, automated linting and validation enforce descriptive outputs, strict variable typing, and input validation rules for Terraform configurations based on your project's coding standards.

What's the best way to scaffold a new Terraform module with security and tagging guardrails?

Scaffold a new Terraform module using templates that automatically include provider configuration, tagging standards, and security best practices alongside the standard module file layout.

Does this approach support Terraform code reviews for infrastructure-as-code projects?

Yes, it supports Terraform code reviews by auditing configurations against coding standards, validating module structure, and checking for proper typing, security practices, and provider configuration.