terraform-resources

Automate Terraform resource declarations, dynamic blocks, meta-arguments, dependencies, timeouts, lifecycle rules, and naming conventions across providers and modules.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/Luscii/terraform-fluentbit-luscii-presets --skill terraform-resources
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terraform-resources
Source: https://github.com/Luscii/terraform-fluentbit-luscii-presets/tree/main/.github/skills/terraform-resources
Command: npx skills add https://github.com/Luscii/terraform-fluentbit-luscii-presets --skill terraform-resources

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Terraform resource configuration patterns reduce boilerplate and prevent misconfigurations across infrastructure as code.

Core Features & Use Cases

  • Standardized resource declarations with clear naming and addressing.
  • Dynamic blocks and loops (for_each, count) to model complex infrastructure without repetition.
  • Meta-arguments, depends_on, timeouts, and lifecycle guidance for predictable deployments.
  • Use cases include multi-subnet VPC setups, scalable databases, and module-friendly resource naming conventions.

Quick Start

  • Review the recommended Terraform resource patterns and apply them to your modules.
  • Run terraform fmt, terraform validate, and plan to verify changes before applying.
  • Adapt the patterns to your organization's naming conventions and module boundaries.

Frequently Asked Questions about terraform-resources

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

FAQPage Schema
How do I use dynamic blocks and for_each in Terraform resource configurations?

Terraform dynamic blocks and for_each loops model complex infrastructure without repetition by dynamically generating nested block configurations. This approach standardizes resource declarations and reduces boilerplate across multi-subnet VPC setups and scalable databases.

What is the best way to manage Terraform resource dependencies and lifecycle rules?

Managing Terraform lifecycle rules involves applying meta-arguments like depends_on, timeouts, and lifecycle settings for predictable deployments. Explicit dependencies ensure deterministic configurations and clear argument ordering across providers and modules.

How do I apply consistent naming conventions to Terraform resources across modules?

Consistent Terraform resource naming requires standardizing declarations with clear addressing and module-friendly naming conventions. Adapting recommended patterns to your organization's module boundaries ensures deterministic configurations across infrastructure as code.

Can I use Terraform meta-arguments to control resource creation and destruction order?

Terraform meta-arguments like depends_on, count, and lifecycle rules control resource creation and destruction order. These arguments provide explicit dependency management and predictable deployment behavior when implicit dependencies are insufficient.

Why does my Terraform plan fail validation after adding dynamic blocks to a resource?

Terraform plan validation fails when dynamic blocks contain invalid argument structures or unsupported attributes. Running terraform fmt, terraform validate, and plan verifies resource configuration changes and catches misconfigurations before applying infrastructure updates.