terraform-module-library

Generate reusable Terraform module scaffolding for AWS, Azure, GCP, and OCI.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Jhabbig/Habbig --skill terraform-module-library-jhabbig
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: terraform-module-library
Source: https://github.com/Jhabbig/Habbig/tree/main/.claude/plugins/wshobson/cloud-infrastructure/skills/terraform-module-library
Command: npx skills add https://github.com/Jhabbig/Habbig --skill terraform-module-library-jhabbig

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the guesswork from building reusable Terraform modules by giving you a consistent, production-ready pattern for cloud infrastructure across multiple providers.

Core Features & Use Cases

  • Multi-cloud module design: Create standardized modules for AWS, Azure, GCP, and OCI using a shared structure.
  • Best-practice scaffolding: Include validated inputs, clear outputs, pinned provider versions, and example usage from the start.
  • Production workflows: Apply it to common infrastructure like VPCs, EKS, RDS, S3, VCNs, OKE, and object storage modules.
  • Use Case: A platform team can use this Skill to rapidly generate a new networking module that matches organizational standards and is ready for reuse across environments.

Quick Start

Ask the Skill to design a reusable Terraform module for your target cloud resource and generate the standard files, examples, validation, and documentation.

Frequently Asked Questions about terraform-module-library

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

FAQPage Schema
How do I build reusable Terraform modules for AWS, Azure, GCP, and OCI?▼

Standardized Terraform modules require documented variables, clear outputs, pinned provider versions, validation rules, and example usage. This structure ensures maintainable infrastructure-as-code delivery across AWS, Azure, GCP, and OCI environments.

What is the best way to structure a production-ready Terraform module?▼

A production-ready Terraform module structure includes validated inputs, clear outputs, pinned provider versions, and example-driven composition. This pattern standardizes resource creation for services like VPCs, EKS, RDS, S3, VCNs, and OKE.

Can I use this approach to create standardized modules for OCI resources like VCNs and OKE?▼

Yes, this approach supports OCI module design by applying provider-specific resource patterns for VCNs, OKE, and object storage. It generates the required files, examples, and validation to ensure modules match organizational standards for reuse.

How do I generate scaffolding for a new networking module that matches organizational standards?▼

You generate module scaffolding by requesting the standard files, examples, and validation for your target cloud resource. The Skill provides a consistent, production-ready pattern for platform teams to rapidly create reusable networking modules.

Do I need to manually add validation and version pinning when designing infrastructure-as-code modules?▼

No, production-ready module scaffolding includes input validation and version pinning by default. This removes the guesswork from infrastructure-as-code delivery and ensures modules are test-friendly and maintainable from the start.

Why does my Terraform module lack a consistent structure across different cloud providers?▼

Without standardized scaffolding, Terraform modules lack consistent structure across providers. Applying a shared structure with documented variables, outputs, and example usage ensures your AWS, Azure, GCP, and OCI modules remain maintainable.