developing-components

Standardize Terraform/OpenTofu component creation with required files and naming conventions.

98|34|Updated Apr 27, 2018
One-click install
npx skills add https://github.com/cloudposse/docs --skill developing-components
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developing-components
Source: https://github.com/cloudposse/docs/tree/main/examples/snippets/.claude/skills/developing-components
Command: npx skills add https://github.com/cloudposse/docs --skill developing-components

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams standardize the creation and modification of Terraform/OpenTofu components by enforcing required files, catalog defaults, stack configuration, and naming conventions.

Core Features & Use Cases

  • Enforces a consistent component structure across projects, including root module layout and context.
  • Guides vendoring, catalog defaults, and stack configuration to simplify reuse.
  • Provides clear naming conventions to improve discoverability and maintainability.

Quick Start

Create the component directory, copy an existing template, and configure catalog defaults to begin.

Frequently Asked Questions about developing-components

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

FAQPage Schema
How do I standardize Terraform component structure across projects?

Standardize Terraform component structure by enforcing required root files, validating module layout, and applying catalog defaults. This ensures consistent, reproducible builds and simplifies component maintenance across your OpenTofu projects.

What naming conventions should I use for Terraform components?

Terraform component naming conventions improve discoverability and maintainability by standardizing directory names and module references. Applying these conventions aligns new components with existing catalog defaults and stack configurations for consistent reuse.

How do I add new OpenTofu components to an existing stack configuration?

Add new OpenTofu components by creating a component directory, copying an existing template, and configuring catalog defaults. This process aligns the new component with your stack configuration and enforces required root files for reproducible builds.

Does this approach work with both Terraform and OpenTofu projects?

Yes, this component standardization process works with both Terraform and OpenTofu projects. It enforces required root files, validates module structure, and aligns catalog defaults across both platforms to ensure consistent builds.

Why do I need to align Terraform components with catalog defaults?

Aligning Terraform components with catalog defaults simplifies reuse and ensures consistent configuration across stack deployments. It enforces required root files and standardizes naming conventions to maintain reproducible builds throughout your project.

What's the best way to manage vendoring and catalog defaults for Terraform modules?

Manage vendoring and catalog defaults by applying standardized component creation practices that guide module reuse. This enforces required root files and validates structure to maintain consistent, reproducible Terraform builds.