terraform-module-builder_skill

Overview

This skill generates production-ready Terraform module templates and complete .tf file sets for AWS, GCP, and Azure infrastructure. It produces opinionated, best-practice configurations (providers, versions, variables, outputs, locals, data sources) and ready-to-use module layouts for common patterns like ECS Fargate, S3+CloudFront static sites, and reusable network stacks. Use it to jumpstart IaC while preserving Terraform 1.5+ standards and sensible defaults.

How this skill works

When triggered, the skill emits a complete Terraform directory structure with main.tf, variables.tf, outputs.tf, providers.tf, versions.tf, locals.tf, data.tf and example terraform.tfvars. It scaffolds modules and resources with clear naming, tags, validations, and backend configuration. Templates include autoscaling, logging, IAM roles, security groups, and optional production protections like deletion protection and state locking.

When to use it

• Bootstrapping infrastructure for a new project across AWS, GCP, or Azure
• Creating reusable Terraform modules for teams or CI/CD pipelines
• Generating secure defaults (state backend, version constraints, tags, IAM roles)
• Scaffolding common workloads such as ECS Fargate, static sites with S3+CloudFront, or VPC modules
• Rapid prototyping of environments with variables and sensible defaults

Best practices

• Keep modules focused and composable—one responsibility per module (network, compute, storage)
• Use remote state backend and state locking for team collaboration
• Define input validation and sensible defaults in variables.tf to prevent misconfiguration
• Tag all resources and expose critical outputs to simplify automation and downstream modules
• Use lifecycle ignore_changes and deployment circuit breaker for safe rolling updates

Example use cases

• Generate an AWS ECS Fargate module with VPC, ALB, IAM, autoscaling, and logging ready to plug into CI
• Create an S3 + CloudFront static website stack with Origin Access Control, SPA error handling, and versioning enabled
• Scaffold a multi-environment module set (dev/staging/prod) with environment validation and production protections
• Produce provider and version-managed templates for GCP or Azure resources following same module layout and output patterns