Can I use it to update existing infrastructure?

Absolutely. It can read existing contexts and implementation guidance to modify current Terraform files or add new resources to your infrastructure directory.

Does this skill validate the generated code?

Yes, the skill automatically runs 'terraform fmt' and 'terraform validate' via shell scripts to ensure the output is syntactically correct and properly formatted.

What is the primary function of the infra-engineer skill?

It translates infrastructure design documents or text instructions into valid, modular Terraform code, including resources, variables, and provider configurations.

Does it follow security best practices?

Yes, it implements standard security patterns such as server-side encryption for S3, least-privilege IAM roles, and comprehensive resource tagging.

Terraform Infrastructure Engineer

Name: Terraform Infrastructure Engineer
Author: fractary

byfractary

•

Cloud Infrastructure

Generates production-ready Terraform infrastructure as code from design documents following modular best practices.

About

The Terraform Infrastructure Engineer skill automates the translation of architectural design specifications into structured, maintainable Terraform configurations. It handles the complete lifecycle of IaC generation, including resource definitions, variable declarations, outputs, and provider setups, while strictly adhering to DRY principles and standardized naming conventions. By utilizing a specialized 3-layer architecture that combines deterministic shell scripts with LLM reasoning, it ensures that all generated code is automatically formatted and validated before delivery, significantly reducing manual DevOps overhead.

Key Features

Automated HCL generation from design documents and FABER specs
Built-in validation using terraform fmt and terraform validate
Deterministic input parsing and security-validated path handling
Modular code structure following DRY principles and best practices
2 GitHub stars
Standardized resource naming, tagging, and organization

Use Cases

Adding and updating cloud resources while maintaining consistent naming patterns
Translating high-level architectural designs into functional Terraform configurations
Generating production-grade IAM roles, S3 buckets, and Lambda functions with security defaults

About

Key Features

Automated HCL generation from design documents and FABER specs
Built-in validation using terraform fmt and terraform validate
Deterministic input parsing and security-validated path handling
Modular code structure following DRY principles and best practices
2 GitHub stars
Standardized resource naming, tagging, and organization

Use Cases

Adding and updating cloud resources while maintaining consistent naming patterns
Translating high-level architectural designs into functional Terraform configurations
Generating production-grade IAM roles, S3 buckets, and Lambda functions with security defaults