terraform-module-library

Create reusable Terraform modules for AWS, Azure, GCP, and OCI infrastructure.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill terraform-module-library-sanketadlak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terraform-module-library
Source: https://github.com/SanketAdlak/PDMProjectDesign/tree/main/.agents/skills/terraform-module-library
Command: npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill terraform-module-library-sanketadlak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing cloud infrastructure from scratch for every project leads to inconsistent, untested Terraform code. This Skill provides standardized module patterns so teams can build reusable, validated infrastructure components across multiple cloud providers. ## Core Features & Use Cases - Multi-Cloud Module Patterns: Standard structures for AWS (VPC, EKS, RDS, S3), Azure (VNet, AKS), GCP (VPC, GKE, Cloud SQL), and OCI (VCN, OKE, Object Storage). - Best-Practice Module Design: Enforces semantic versioning, input validation blocks, pinned provider versions, consistent tagging, and documented variables and outputs. - Testing with Terratest: Includes Go-based Terratest patterns to validate modules through automated init, apply, and destroy cycles. - Use Case: A platform engineer needs a production VPC on AWS. Use this Skill to generate a VPC module with validated CIDR variables, private subnets, an Internet Gateway, tagged resources, and a Terratest suite. ## Quick Start Ask the AI to create a reusable Terraform VPC module for AWS with input validation, outputs, and a Terratest test file.

Frequently Asked Questions about terraform-module-library

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a reusable Terraform module for AWS?

Structure the module with main.tf, variables.tf, outputs.tf, and versions.tf files. Add validation blocks for inputs like CIDR blocks, document every variable, expose key attributes as outputs, and include an examples directory plus Terratest tests.

What is the standard structure of a Terraform module?

A standard module contains main.tf for resources, variables.tf for inputs, outputs.tf for exported values, versions.tf for provider constraints, a README, an examples/complete directory, and a tests directory with Terratest Go files.

How do I test Terraform modules with Terratest?

Write a Go test using the gruntwork-io/terratest terraform package. Point TerraformDir at your examples/complete folder, run InitAndApply, assert on outputs like vpc_id, and defer terraform.Destroy to clean up resources.

Does this support Oracle Cloud Infrastructure Terraform modules?

Yes, it includes OCI module patterns for VCN, OKE, Autonomous Database, Object Storage, and Load Balancer. It recommends OCI provider version ~> 7.26, explicit compartment modeling, NSGs, and least-privilege dynamic groups.

What Terraform best practices should modules follow?

Use semantic versioning, validate inputs with validation blocks, pin provider versions, tag all resources consistently, use count and for_each for conditional resources, and test modules with Terratest before release.