Skip to content
Skills Library
DevOps & cloud · Building & coding

infrastructure-as-code

/infrastructure-as-code

Manage infrastructure through declarative code with sane module design, state hygiene, and plan-review discipline. Use when adopting Terraform-style IaC or refactoring a sprawling configuration.

Repository
AI-SKILLS ↗
Licence
MIT
Last repository change
05.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Manage infrastructure through declarative code with sane module design, state hygiene, and plan-review discipline. Use when adopting Terraform-style IaC or refactoring a sprawling configuration.

Original author description

Manage infrastructure through declarative code with sane module design, state hygiene, and plan-review discipline. Use when adopting Terraform-style IaC or refactoring a sprawling configuration.

How it works

  1. Method
  2. Boundaries
Original SKILL.md headings · 57 lines, 419 words
SKILL.md preview
---
name: infrastructure-as-code
description: Manage infrastructure through declarative code with sane module design, state hygiene, and plan-review discipline. Use when adopting Terraform-style IaC or refactoring a sprawling configuration.
---

# Infrastructure as code

The repository is the source of truth; the cloud is a cache of it.
Everything follows from defending that invariant: no console edits, no
unreviewed applies, no state nobody owns.

## Method

1. **Structure as small root modules per blast radius.** One state per
   environment per subsystem (`prod/network`, `prod/database`,
   `staging/app`), not one monolithic state: applies stay fast, locks
   stay short, and a bad change cannot touch what its state does not
   hold. Compose from reusable child modules with explicit
   inputs/outputs.
2. **Design modules like APIs.** Few required variables, safe defaults
   (encryption on, public access off), validation blocks on inputs,
   documented outputs consumed by other stacks via remote state or
   data sources. A module needing 40 variables is a template, not an
   abstraction; split it.
3. **Guard the state like production data.** Remote backend with
   locking and versioning, encrypted, access-controlled (state contains
   secrets in plaintext more often than teams admit). Never edit state
   by hand; `state mv`/`import` for surgery, with a second person
   watching.
4. **Make plan review the real gate.** CI posts the plan on the PR;
   humans review the diff (destroys and replaces especially: know why
   an attribute forces replacement before approving), then CI applies
   the *same saved plan* on merge. Fresh-plan-at-apply can differ from
   what was reviewed. Pipeline detail in gitops-workflow and
   deployment-pipelines.
5. **Hunt drift on a schedule.** Nightly `plan` in CI alerting on
   non-empty diffs; drift means console edits or an outside actor,
   both worth investigating, then reconciling (import or revert) the
   same week. Standing drift teaches everyone the repo is a suggestion.
6. **Version and pin everything.** Providers and modules pinned
   (lockfiles committed), upgrades as deliberate PRs; tag module
   releases so consumers upgrade on their schedule. Policy-as-code
   checks (deny public buckets, require tags; see iam-design
   boundaries) run in CI where they cannot be skipped.
7. **Test at the right altitude.** Static: fmt, validate, lint,
   policy. Integration: spin ephemeral stacks for the modules whose
   failure is expensive (network, IAM). Do not chase 100% "unit
   coverage" on declarative code; the plan diff is the test for most
   changes.

## Boundaries

- Application deploys move faster than infrastructure; keep app config
  out of the infra state (see config-management) or every release
  waits on an infra lock.
- Imperative escape hatches (provisioners, local-exec scripts) trade
  idempotency away; quarantine them behind their own small stacks
  with documented manual recovery.
- IaC will not fix an unowned platform; every state file needs a team
  on its review path, or drift and secrets rot in the dark.

Versions

RepositoryScoreLicence
This page · Amey-Thakur/AI-SKILLS90MIT
atretyak1985/swarmery100Apache-2.0
peterbamuhigire/chwezi-dev-engine100MIT
Rene-Roscher/skills100Apache-2.0
arjunprabhulal/devops-skills100MIT
seb1n/awesome-ai-agent-skills100MIT
MARUCIE/openclaw-foundry100MIT
kid-sid/codex-spellbook100MIT
wrongstack/wrongstack90MIT

Database snapshot: 13.11.2026 · package version 77b6d373b823 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100terraform-iac
    Manages cloud infrastructure using Terraform (and OpenTofu). Use when the user wants to write Terraform configurations, provision cloud resources, manage state, create modules, set up multi-environment deployments, import existing infrastructure, debug plan/apply errors, migrate…
  • 100infrastructure-as-code-terraform
    Authors, structures, and safely applies Terraform infrastructure-as-code, including module design, remote state, workspaces, plan review, and importing existing resources. Use when the user asks to "write Terraform for X," "structure a Terraform repo/modules," "manage remote…
  • 100terraform-iac-expert
    Expert in Infrastructure as Code using Terraform and OpenTofu. Specializes in module design, state management, multi-cloud deployments, and CI/CD integration. Handles complex infrastructure patterns including multi-environment setups, remote state backends, and secure secrets…
  • 95terraform-patterns
    Terraform infrastructure-as-code agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Covers module design patterns, state management strategies, provider configuration, security hardening, policy-as-code with Sentinel/OPA, and CI/CD plan/apply workflows.…
  • 95terraform-patterns
    Terraform infrastructure-as-code agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Covers module design patterns, state management strategies, provider configuration, security hardening, policy-as-code with Sentinel/OPA, and CI/CD plan/apply workflows.…
  • 100infrastructure-terraform
    Terraform IaC: HCL, state management, modules, plan-apply workflows. Use when the user mentions Terraform, HCL, terraform plan/apply, tfstate, or IaC provisioning.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.