terraform-engineer

Name: terraform-engineer
Availability: InStock
Author: jeffallan

Automate modular Terraform development and remote state management across AWS, Azure, and GCP.

10.9k|1.0k|Updated Oct 20, 2025

Search Tags:#IaC #Terraform #state #terraform module #Azure provider #AWS provider #GCP provider

Ready to run

npx skills add https://github.com/Jeffallan/claude-skills --skill terraform-engineer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: terraform-engineer
Source: https://github.com/Jeffallan/claude-skills/tree/main/skills/terraform-engineer
Command: npx skills add https://github.com/Jeffallan/claude-skills --skill terraform-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill teaches modular Terraform design, remote state management, and multi-environment workflows for reliable infrastructure as code.

Core Features & Use Cases

Modules: Reusable Terraform modules with clear interfaces.
State Management: Remote state with locking, backends, and workspaces.
Providers: AWS/Azure/GCP configuration and multi-cloud provisioning.
Testing: Plan validation and policy-as-code patterns.

Quick Start

Build a reusable VPC module with inputs for region, CIDR, and tags; wire a test environment.

Frequently Asked Questions about terraform-engineer

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

FAQPage Schema

How do I structure reusable Terraform modules for multi-cloud infrastructure?▼

Reusable Terraform modules encapsulate infrastructure logic with clear input variables and outputs, enabling consistent deployment across AWS, Azure, and GCP. Define module interfaces with required inputs (region, CIDR, tags), test them independently, and version them semantically to support reproducible multi-environment workflows.

What's the best way to manage Terraform state across multiple environments?▼

Remote state backends with locking prevent concurrent modifications and enable team collaboration. Configure backends for each environment using workspaces or separate state files, enable state locking on supported backends (S3, Azure Storage, GCS), and encrypt state at rest to protect sensitive infrastructure data.

Can I use Terraform to provision infrastructure across AWS, Azure, and GCP simultaneously?▼

Yes, Terraform supports multi-cloud provisioning through provider configuration. Configure AWS, Azure, and GCP providers in a single codebase, use modules to abstract provider-specific details, and manage state centrally to orchestrate resources across all three clouds in coordinated deployments.

How do I validate and test Terraform infrastructure as code before deployment?▼

Infrastructure as code testing includes plan validation, policy-as-code checks (OPA, Sentinel), and automated testing frameworks (Terratest, tflint). Run terraform plan to preview changes, integrate policy enforcement to catch misconfigurations, and execute integration tests to verify module behavior and compliance requirements.

Why should I enforce semantic versioning and naming conventions in Terraform modules?▼

Semantic versioning and consistent naming enable teams to manage breaking changes, track module evolution, and reuse infrastructure code reliably. Versioning signals compatibility; standardized naming (resource prefixes, tag schemas) ensures consistency across multi-environment deployments and simplifies state management.

Do I need to manage secrets separately when using Terraform with cloud providers?▼

Yes, secrets management is critical for production infrastructure. Store sensitive data (API keys, credentials) outside Terraform state using cloud provider secret services or external vaults, reference them via data sources, and encrypt state files to prevent accidental exposure in version control.