Designing complex Terraform modules for multi-cloud setups.
Terraform Module Architect
Terraform, Terragrunt, Multi-cloud
Best for
- ▸Designing multi-cloud Terraform modules with consistent provider patterns across AWS, Azure, GCP
- ▸Implementing Terragrunt-based DRY architectures for enterprise infrastructure code organization
- ▸Setting up drift detection pipelines with automated remediation workflows for production environments
- ▸Building workspace strategies for team-based Terraform deployments with proper state isolation
What you'll get
- ▸Complete module directory structure with variables.tf, outputs.tf, main.tf showing composition patterns, plus versioning strategy and registry setup
- ▸Terragrunt configuration hierarchy with environment-specific terragrunt.hcl files, remote state configuration, and dependency management
- ▸CI/CD pipeline YAML with drift detection jobs, state validation steps, and automated remediation workflows with alerting integration
Infrastructure requirements including scale (team size, environment count), cloud providers, existing Terraform setup, and specific challenges with state management or module composition.
Detailed Terraform module architecture with code examples, state management strategy, Terragrunt configuration patterns, and implementation roadmap with testing approaches.
What's inside
“You are a Terraform Module Architect. You design composable, production-grade Terraform modules, manage state at scale across hundreds of workspaces, detect and remediate infrastructure drift, and establish provider patterns for multi-cloud and multi-account environments. - **Compose over monoliths*...”
Covers
Not designed for ↓
- ×Writing basic Terraform resources or simple configurations (use terraform-infrastructure-architect instead)
- ×Cloud-specific infrastructure design without Terraform module architecture considerations
- ×Day-to-day operational tasks like applying Terraform plans or troubleshooting resource creation
- ×Non-Terraform infrastructure-as-code tools like Pulumi, CloudFormation, or ARM templates
SupaScore
89.03▼
Evidence Policy
Standard: no explicit evidence policy.
Research Foundation: 8 sources (4 official docs, 2 books, 2 industry frameworks)
This skill was developed through independent research and synthesis. SupaSkills is not affiliated with or endorsed by any cited author or organisation.
Version History
v5.5 distilled from v2 via Claude Sonnet
Pipeline v4: rebuilt with 3 helper skills
Initial release
Prerequisites
Use these skills first for best results.
Works well with
Need more depth?
Specialist skills that go deeper in areas this skill touches.
Common Workflows
Enterprise Infrastructure Modernization
Transform legacy infrastructure to modern IaC with proper module architecture, GitOps workflows, and automated deployment pipelines
© 2026 Kill The Dragon GmbH. This skill and its system prompt are protected by copyright. Unauthorised redistribution is prohibited. Terms of Service · Legal Notice