terraform-module-library
Build reusable Terraform modules
Teams struggle to standardize Terraform modules across clouds. This skill provides patterns, examples, and testing guidance to create reusable infrastructure modules.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "terraform-module-library". Create a reusable AWS VPC module plan
Expected outcome:
- Module layout with main.tf, variables.tf, outputs.tf, versions.tf, examples/, and tests/
- Key variables: name, cidr_block, availability_zones, private_subnet_cidrs with validation
- Essential outputs: vpc_id, private_subnet_ids, vpc_cidr_block for composition
- Testing checklist using Terratest with assertions for VPC ID presence and CIDR validation
Using "terraform-module-library". Design multi-cloud module standards
Expected outcome:
- Use semantic versioning and pin provider versions for consistency
- Document all inputs and outputs with clear descriptions for consumers
- Include working examples showing how to invoke each module
- Add Terratest cases covering happy path and edge cases
Security Audit
SafeDocumentation-only skill containing markdown files with Terraform patterns and examples. No executable code (.tf, .go, .sh files present). Static findings are all false positives triggered by documentation text patterns (Terraform resource names, module paths, example CIDR blocks). Content matches stated purpose of providing IaC guidance.
Risk Factors
⚡ Contains scripts (1)
🌐 Network access (1)
📁 Filesystem access (1)
⚙️ External commands (1)
Quality Score
What You Can Build
Standardize AWS modules
Create consistent Terraform module structures and examples for shared AWS infrastructure across teams.
Define module standards
Set documentation, testing, and versioning conventions for reusable Terraform modules organization-wide.
Design module composition
Plan how VPC, database, and compute modules connect to form complete environments.
Try These Prompts
Provide a standard Terraform module folder structure for an AWS VPC module including examples and tests.
List required and optional variables for an AWS VPC module with validation guidance for CIDR blocks.
Outline a Terratest plan for a VPC module including key assertions for VPC ID and subnet outputs.
Show how to compose VPC and RDS modules with shared tags and cross-module outputs for production.
Best Practices
- Document all inputs and outputs with clear descriptions for module consumers
- Use semantic versioning and pin provider versions in versions.tf
- Include working example configurations and automated tests with Terratest
Avoid
- Embedding environment-specific values like account IDs or region directly in module code
- Omitting input validation for critical variables like CIDR blocks or instance sizes
- Publishing modules without example usage showing how to invoke them