Design Terraform modules people reuse

Steps

1. 1One module = one architectural decision (a network, a service, a store)
2. 2Type every variable; constrain with validation blocks
3. 3Defaults for 80% cases; no secret values as defaults ever
4. 4Outputs expose only what callers genuinely consume
5. 5Tag resources uniformly: env, owner, repo, cost-center
6. 6Version modules semver; changelog breaking moves loudly

Common Pitfalls

• ▲Copy-pasted 800-line root modules nobody dares touch
• ▲count vs for_each migrations destroying remote state

Commands

$ npx skills add aniruddhaadak80/skills --skill infrastructure-as-code-terraform-module-design

$ npx skills add aniruddhaadak80/skills --skill infrastructure-as-code-terraform-module-design -g

Tags