How do I install the Terraform Module skill?

Run npx skillmds@latest add bitwise-media-group/terraform-module in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Terraform Module safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Terraform Module?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Terraform Module free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Terraform Module?

bitwise-media-group (@bitwise-media-group) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Terraform Module by bitwise-media-group

Name: Terraform Module
Author: bitwise-media-group

Terraform Module

Scaffold a new Terraform module with the canonical file layout — terraform.tf, main.tf, variables.tf, outputs.tf, README.md — and house style. Use when creating a new Terraform module, adding a module under a modules/ directory, or restructuring an existing module to the standard layout.

bitwise-media-group 84e956b 6 files · 6.5 KB Updated Sep 17, 2026

File contents

Scaffold a Terraform module

Creates a module with the canonical five-file layout. Apply the terraform-style skill's conventions while filling in real content, and finish with the terraform-validate workflow.

1. Name the module and pick providers

Directory: kebab-case, named for what the module manages (modules/ecr-registry, not modules/registry-stuff). One cohesive concern per module.
Decide which providers the module needs and their major-version constraints before writing resources — they go in terraform.tf on day one.

2. Create the five canonical files

Copy the skeletons from this skill's templates/ directory into the new module directory and replace the placeholder content:

File	Template shows
`terraform.tf`	`required_version` + `required_providers` with major-version pins
`main.tf`	a primary resource named `main`, plus naming-convention reminders
`variables.tf`	a required flat variable, an object variable with `optional()` defaults
`outputs.tf`	flat primary-attribute outputs and one grouped object output
`README.md`	title, purpose paragraph, Usage example, Inputs/Outputs tables

Every variable and output keeps a description — the linter enforces this.

3. Apply the house style

While implementing, follow the terraform-style skill. The rules that most often shape a new module's interface:

set(string) for unordered unique inputs; primary resource named main;
name_prefix (trailing -) for account-unique named resources;
boolean-gated resources via for_each = toset(var.x ? ["true"] : []);
outputs named for the attribute, cohesive facets grouped into one object;
optional strings default to null, never "".

Split cohesive resource families into domain files (iam-node.tf, signing.tf) once main.tf grows past a screenful — the five canonical files are the floor, not the ceiling.

4. Document and validate

Fill in the README's Usage example with a realistic call (module "x" { source = "../..." }) showing only the inputs a typical caller sets.
Run the terraform-validate workflow (fmt → init/validate → tflint) on the new module before committing.

---name: terraform-moduledescription: Scaffold a new Terraform module with the canonical file layout — terraform.tf, main.tf, variables.tf, outputs.tf, README.md — and house style. Use when creating a new Terraform module, adding a module under a modules/ directory, or restructuring an existing module to the standard layout.license: MIT---# Scaffold a Terraform moduleCreates a module with the canonical five-file layout. Apply the `terraform-style` skill'sconventions while filling in real content, and finish with the `terraform-validate` workflow.## 1. Name the module and pick providers- Directory: kebab-case, named for what the module manages (`modules/ecr-registry`, not `modules/registry-stuff`). One cohesive concern per module.- Decide which providers the module needs and their major-version constraints before writing resources — they go in `terraform.tf` on day one.## 2. Create the five canonical filesCopy the skeletons from this skill's [templates/](templates/) directory into the new moduledirectory and replace the placeholder content:| File | Template shows || --- | --- || `terraform.tf` | `required_version` + `required_providers` with major-version pins || `main.tf` | a primary resource named `main`, plus naming-convention reminders || `variables.tf` | a required flat variable, an object variable with `optional()` defaults || `outputs.tf` | flat primary-attribute outputs and one grouped object output || `README.md` | title, purpose paragraph, Usage example, Inputs/Outputs tables |Every variable and output keeps a `description` — the linter enforces this.## 3. Apply the house styleWhile implementing, follow the `terraform-style` skill. The rules that most often shape a newmodule's interface:- `set(string)` for unordered unique inputs; primary resource named `main`;- `name_prefix` (trailing `-`) for account-unique named resources;- boolean-gated resources via `for_each = toset(var.x ? ["true"] : [])`;- outputs named for the attribute, cohesive facets grouped into one object;- optional strings default to `null`, never `""`.Split cohesive resource families into domain files (`iam-node.tf`, `signing.tf`) once `main.tf`grows past a screenful — the five canonical files are the floor, not the ceiling.## 4. Document and validate- Fill in the README's Usage example with a realistic call (`module "x" { source = "../..." }`) showing only the inputs a typical caller sets.- Run the `terraform-validate` workflow (fmt → init/validate → tflint) on the new module before committing.

Frequently asked questions