Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/devops/infrastructure-as-code-generator/skills/generating-infrastructure-as-code

generating-infrastructure-as-code

Verified

Execute use when generating infrastructure as code configurations. Trigger with phrases like "create Terraform config", "generate CloudFormation template", "write Pulumi code", or "IaC for AWS/GCP/Azure". Produces production-ready code for Terraform, CloudFormation, Pulumi, ARM templates, and CDK across multiple cloud providers.

Generating Infrastructure as Code

Overview

Generate production-ready infrastructure as code for Terraform, CloudFormation, Pulumi, ARM templates, and AWS CDK. Produce modular, well-structured configurations with proper variable definitions, outputs, remote state management, and deployment guidance for AWS, GCP, and Azure cloud stacks.

Prerequisites

  • Target cloud provider CLI installed and authenticated (aws, gcloud, az)
  • IaC tool installed: Terraform 1.0+, Pulumi 3+, AWS CDK, or relevant SDK
  • Cloud credentials configured with permissions to create the target resources
  • Understanding of the desired infrastructure architecture (compute, networking, storage, database)
  • Version control repository for storing IaC configurations

Instructions

  1. Identify the IaC tool and cloud provider based on the project requirements and existing codebase
  2. Scan the project for existing IaC files to understand current patterns and conventions
  3. Define the modular file structure: separate files for providers, networking, compute, storage, and databases
  4. Generate the provider configuration with version pinning and remote backend for state storage
  5. Define input variables with types, descriptions, defaults, and validation rules for all configurable values
  6. Write resource definitions following cloud provider best practices: encryption enabled, logging configured, least-privilege IAM
  7. Add outputs for resource identifiers, endpoints, and connection strings needed by other modules or applications
  8. Configure remote state backend: S3 + DynamoDB for Terraform, Pulumi Cloud, or CloudFormation stack exports
  9. Create environment-specific variable files (terraform.tfvars, dev.tfvars, prod.tfvars) for multi-environment deployment
  10. Validate with terraform validate, terraform plan, or equivalent tool-specific linting

Output

  • IaC configuration files organized by resource type or module
  • Variable definition files with documented inputs and sensible defaults
  • Output definitions for cross-module references and application configuration
  • Backend configuration for remote state storage
  • Environment-specific variable files for dev, staging, and production
  • Deployment instructions with prerequisite setup and apply commands

Error Handling

ErrorCauseSolution
Invalid HCL syntaxMalformed Terraform configurationRun terraform validate to identify the error; check bracket matching and attribute syntax
Unable to authenticate with cloud providerMissing or expired credentialsRun aws configure, gcloud auth login, or az login to refresh credentials
Resource already existsTrying to create a resource that exists outside of IaC managementUse terraform import to bring the existing resource under management
Error acquiring state lockAnother process holding the state lockWait for the other process to finish; use terraform force-unlock <ID> if the lock is stale
Dependency cycle detectedResources referencing each other circularlyRefactor to remove the cycle; use data sources or depends_on to establish explicit ordering

Examples

  • "Generate Terraform for a production VPC on AWS with public/private subnets across 3 AZs, NAT gateways, VPC flow logs, and an EKS cluster."
  • "Create a CloudFormation template for an S3 bucket with versioning, server-side encryption (KMS), public access block, and lifecycle rules."
  • "Write Pulumi TypeScript code for a GCP Cloud Run service with a custom domain, Cloud SQL database, and Secret Manager integration."

Resources

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall