- Home
- Skills
- First Fluke
- Fullstack Starter
- Terraform Module Creator
terraform-module-creator_skill
- TypeScript
181
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill first-fluke/fullstack-starter --skill terraform-module-creator- SKILL.md1.2 KB
Overview
This skill scaffolds new Terraform modules with a standardized directory and file layout that complements an existing module library. It generates the basic files (main, variables, outputs, versions) and a README to jumpstart consistent, production-ready modules. The goal is fast, repeatable module creation that aligns with established patterns and provider requirements.
How this skill works
The skill creates a modules/<module-name> folder and generates main.tf, variables.tf, outputs.tf, versions.tf, and README.md with sensible defaults. versions.tf pins Terraform and provider constraints, variables.tf defines common inputs like project_id, and outputs.tf exposes typical resource identifiers. Use this generator for the initial scaffolding, then refine logic and patterns using the module library.
When to use it
- Starting a new Terraform module in a monorepo or modules collection
- Onboarding contributors to ensure consistent module structure
- Quickly prototyping infrastructure resources before adding implementation
- Standardizing provider and Terraform version constraints across modules
- Automating repository templates for multiple cloud projects
Best practices
- Keep the scaffolded files minimal; implement resource logic in main.tf after scaffolding
- Use versions.tf to enforce required Terraform and provider versions for safety
- Define clear, typed variables with descriptions and sensible defaults when possible
- Expose only necessary outputs to keep module surface area small
- Follow design and code patterns from the module library for complex logic and testing
Example use cases
- Create a Google Cloud VM module scaffold with project_id variable and output for resource ID
- Add a new networking module to the monorepo using the standard file layout
- Provide new team members with a repeatable template for building modules
- Automate generation of multiple modules during project bootstrapping
- Ensure consistent provider constraints across all new modules in the repository
FAQ
No. The scaffold creates the structure and common files; you add provider-specific resources in main.tf following library patterns.
Can I change the versions or providers after scaffolding?
Yes. versions.tf is a starting point; update required_version and required_providers to match your project needs.