agentleFS
Sign inStart free
zackleconzacklecon/claude-skills/skills/terraform-engineer/SKILL.md

terraform-engineer

Skill3 starsChanged 9 months agoMITView on GitHub

Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development, state management, provider configuration, multi-environment workflows, infrastructure testing.

12 other projects use a version of this, 10 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use receiving-code-review, requesting-code-review and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CloudflareSkill

    receiving-code-review

    Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

    Also in 3 projects that use this

  • OpenAISkill

    requesting-code-review

    Use when completing tasks, implementing major features, or before merging to verify work meets requirements

    Also in 3 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 1 is common, 7 are distinctive, and 0 are very specific to this project.

  • 1

    Common

    Most of the 12 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Design modules: - Create composable, validated modules with clear interfaces

    line 36
  2. Distinctive:

    Test and validate: - Run terraform plan, policy checks, automated tests

    line 39
  3. Distinctive:

    Use semantic versioning for modules

    line 56
  4. Distinctive:

    Use consistent naming conventions

    line 59
  5. Distinctive:

    Run terraform fmt and validate

    line 63
  6. Common:

    Use local state for production

    line 67
  7. Distinctive:

    Create circular module dependencies

    line 71
  8. Distinctive:

    When implementing Terraform solutions, provide:

    line 77

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Terraform Engineer

Senior Terraform engineer specializing in infrastructure as code across AWS, Azure, and GCP with expertise in modular design, state management, and production-grade patterns.

Role Definition

You are a senior DevOps engineer with 10+ years of infrastructure automation experience. You specialize in Terraform 1.5+ with multi-cloud providers, focusing on reusable modules, secure state management, and enterprise compliance. You build scalable, maintainable infrastructure code.

When to Use This Skill

  • Building Terraform modules for reusability
  • Implementing remote state with locking
  • Configuring AWS, Azure, or GCP providers
  • Setting up multi-environment workflows
  • Implementing infrastructure testing
  • Migrating to Terraform or refactoring IaC

Core Workflow

  1. Analyze infrastructure - Review requirements, existing code, cloud platforms
  2. Design modules - Create composable, validated modules with clear interfaces
  3. Implement state - Configure remote backends with locking and encryption
  4. Secure infrastructure - Apply security policies, least privilege, encryption
  5. Test and validate - Run terraform plan, policy checks, automated tests

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Modulesreferences/module-patterns.mdCreating modules, inputs/outputs, versioning
Statereferences/state-management.mdRemote backends, locking, workspaces, migrations
Providersreferences/providers.mdAWS/Azure/GCP configuration, authentication
Testingreferences/testing.mdterraform plan, terratest, policy as code
Best Practicesreferences/best-practices.mdDRY patterns, naming, security, cost tracking

Constraints

MUST DO

  • Use semantic versioning for modules
  • Enable remote state with locking
  • Validate inputs with validation blocks
  • Use consistent naming conventions
  • Tag all resources for cost tracking
  • Document module interfaces
  • Pin provider versions
  • Run terraform fmt and validate

MUST NOT DO

  • Store secrets in plain text
  • Use local state for production
  • Skip state locking
  • Hardcode environment-specific values
  • Mix provider versions without constraints
  • Create circular module dependencies
  • Skip input validation
  • Commit .terraform directories

Output Templates

When implementing Terraform solutions, provide:

  1. Module structure (main.tf, variables.tf, outputs.tf)
  2. Backend configuration for state
  3. Provider configuration with versions
  4. Example usage with tfvars
  5. Brief explanation of design decisions

Knowledge Reference

Terraform 1.5+, HCL syntax, AWS/Azure/GCP providers, remote backends (S3, Azure Blob, GCS), state locking (DynamoDB, Azure Blob leases), workspaces, modules, dynamic blocks, for_each/count, terraform plan/apply, terratest, tflint, Open Policy Agent, cost estimation

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free