01
Author maintainable configuration
Create modules, resources, data sources, variables, outputs, locals, provider constraints, validation, and readable documentation.
Terraform infrastructure as code
CategoryCloud & DevOps
Terraform Codex Skills
Terraform Codex Skills help Codex write, review, test, and plan infrastructure changes without treating configuration as ordinary application code. Download the skills for modules, providers, variables, state boundaries, imports, formatting, validation, tests, execution plans, policy checks, and controlled applies.
TerraformInfrastructure as codeExecution plansModules
01
02
03
04
05
06
07
08
09
02
03
04
05
06
07
08
09
task: complete terraform infrastructure as code task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffWhy a specialist workflow matters
A syntactically valid Terraform edit can still replace resources, expose secrets, drift from state, cross workspace boundaries, or create infrastructure with real cost.
Terraform’s core workflow separates writing from planning and applying so the proposed infrastructure actions can be reviewed before any remote change.
These skills keep provider versions, state, workspaces, module contracts, lifecycle behavior, and plan evidence visible before approval.
What the downloadable skills can do
What Terraform Codex Skills can help accomplish
02
Reason about state and change
Inspect addresses, dependencies, imports, moves, lifecycle rules, workspaces, backends, drift, and replacement risk.
03
Validate and test modules
Run formatting, initialize safely, validate syntax and types, write Terraform tests, use mocks where suitable, and check policies.
04
Prepare reviewable plans
Select the correct workspace and variables, generate a plan, summarize creates, updates, destroys, unknowns, sensitive data, and apply boundaries.
A repeatable working process
How the terraform infrastructure as code workflow moves from request to verified result
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
workflow.statusREADY
Context → Plan → Work → Verify
01
Map the infrastructure context
Confirm Terraform and provider versions, backend, workspace, state ownership, modules, credentials source, variables, and environment.
02
Design the desired change
Define resources and invariants, module interfaces, migration or import steps, dependencies, security, cost, and rollback.
03
Format, validate, and test
Run terraform fmt, initialize with appropriate backend behavior, validate, execute relevant tests, and inspect static or policy checks.
04
Generate a plan for approval
Create the plan with the intended inputs, review every destructive or replacement action, and hand off the exact approved artifact.
Useful across real projects
Where Terraform Codex Skills fit
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Reusable modules
Build versioned interfaces, validation, tests, examples, documentation, and compatibility promises.
Cloud infrastructure
Manage compute, networking, identity, storage, databases, observability, and provider-specific constraints.
Platform environments
Coordinate workspaces, state backends, shared services, policy, secrets, CI, and promotion across environments.
Imports and migrations
Bring existing resources under management, move addresses, split state, upgrade providers, and prevent unintended recreation.
Common requests
Tasks these skills can handle
Start with one defined outcome and provide the source material, constraints, and checks that matter.
01Create a Terraform module
02Add variable validation
03Format and validate configuration
04Write Terraform tests
05Import an existing resource
06Review a Terraform plan
07Diagnose state drift
08Prepare a provider upgrade
Who benefits most
Who Is This For?
These skills are designed for people who need dependable terraform infrastructure as code work with a visible process.
Infrastructure engineers
Create reviewable configuration and plans with state and lifecycle effects understood.
Platform teams
Standardize modules, environments, policy checks, CI plans, and approval boundaries.
Cloud developers
Make scoped infrastructure changes without bypassing operational controls.
Security and FinOps reviewers
Inspect identity, exposure, encryption, destructive actions, and cost-relevant plan changes.
Good to know:
The skills will not run apply or destroy without explicit approval, expose secrets or state contents unnecessarily, or assume a plan is safe without the correct workspace, variables, provider access, and review.
Set up the workflow
Installation Guide
Install the complete skill folder and add the project-specific context before beginning.
Download the Terraform skill folder
Keep configuration, modules, state, testing, planning, and apply-safety guidance together.
Install it with the infrastructure repository
Project scope lets the workflow follow versions, modules, backend rules, variables, policy, and CI.
Document environment boundaries
Specify workspaces, accounts, regions, state owners, credentials handling, cost controls, and approval requirements.
List safe checks and commands
Add fmt, init mode, validate, test, policy, security, plan, plan-review, and authorized apply procedures.
Before you download
Frequently Asked Questions
Practical answers about capabilities, limits, setup, and review.
Can the skills write Terraform modules?+
Yes. They cover inputs, outputs, resources, versions, validation, tests, examples, and documentation.
Will they run terraform apply?+
Only after explicit authorization for the exact reviewed environment and plan.
What is the difference between validate and plan?+
Validate checks syntax and internal consistency. Plan evaluates configuration with a workspace, state, variables, and provider APIs to show proposed actions.
Can Terraform tests create real infrastructure?+
They can, depending on the test design. The workflow identifies that risk and requires controlled credentials, cleanup, and cost review.
Can the skills help with imports and moved resources?+
Yes. They map addresses and state transitions carefully to avoid accidental recreation.
Make the work repeatable
Give Codex a Terraform workflow that treats every edit as a proposed infrastructure change proven by tests and an inspected plan.
Clear context. Purposeful work. Relevant checks. A result others can understand.