Quick reference for Terraform conventions including file organization, naming, modules, state, security, and anti-patterns. Use when writing or reviewing Terraform code.
日本語の概要は準備中です。原文の説明を表示しています。
225 件 ・ 関連度順
概要と使いどころ
Quick reference for Terraform conventions including file organization, naming, modules, state, security, and anti-patterns. Use when writing or reviewing Terraform code.
日本語の概要は準備中です。原文の説明を表示しています。
PR review checklist for Terraform changes covering structure, state safety, security, naming, modules, variables, providers, and CI/CD. Use when reviewing Terraform PRs or doing pre-merge checks.
日本語の概要は準備中です。原文の説明を表示しています。
Apply Terraform module structure, state management, and variable patterns for infrastructure as code. Use when writing Terraform.
日本語の概要は準備中です。原文の説明を表示しています。
Terraform best practices: state, security, modules, workflow, testing, tooling. Use when writing or reviewing Terraform code.
日本語の概要は準備中です。原文の説明を表示しています。
Provision and manage cloud infrastructure using Terraform with HCL modules, remote state backends, workspaces, and plan/apply workflow. Implement infrastructure as code patterns with variable management, output values, and state locking for team collaboration. Use when provisioning new cloud infrastructure, migrating from ClickOps or CloudFormation to declarative IaC, managing multi-environment infrastructure, versioning infrastructure changes alongside application code, or enforcing standards through reusable modules.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, reviewing, or generating Terraform HCL that must pass fmt and validate. Not for module authoring, state operations, `terraform apply`, or remote state.
日本語の概要は準備中です。原文の説明を表示しています。
Use Terraform/IaC for Volcengine resources only when the user explicitly chooses Terraform/IaC, already has a Terraform workflow/state, or confirms they need plan/diff/drift/destroy safety for VKE, managed databases/cache/storage, load balancers, domains/certificates, logging/monitoring, or team-managed infrastructure.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing Terraform — AWS modules, resources, variables, outputs, remote state — even when the user just says 'provision this infra' or 'add an S3 bucket' without naming Terraform.
日本語の概要は準備中です。原文の説明を表示しています。
Auditing Terraform infrastructure-as-code for security misconfigurations using Checkov, tfsec, Terrascan, and OPA/Rego policies to detect overly permissive IAM policies, public resource exposure, missing encryption, and insecure defaults before cloud deployment.
日本語の概要は準備中です。原文の説明を表示しています。
Infrastructure as Codeベストプラクティスに従って、AWS、Azure、GCPインフラ用の再利用可能なTerraformモジュールを構築します。インフラモジュール作成、クラウドプロビジョニング標準化、再利用可能なIaCコンポーネント実装時に使用します。
Use when working with Tfsec — tfsec Terraform security scanning. Covers static analysis of Terraform code, custom rule creation, CI integration, severity filtering, module scanning, and remediation guidance. Use when scanning Terraform configurations for security issues, creating custom security rules, or integrating security checks into CI pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
Auditing Terraform infrastructure-as-code for security misconfigurations using Checkov, tfsec, Terrascan, and OPA/Rego policies to tespit etmeoverly permissive IAM policies, public resource exposure, missing encryption, and insecure defaults before cloud Dağıt:ment.
日本語の概要は準備中です。原文の説明を表示しています。
Auditing Terraform infrastructure-as-code for security misconfigurations using Checkov, tfsec, Terrascan, and OPA/Rego policies to detect overly permissive IAM policies, public resource exposure, missing encryption, and insecure defaults before cloud deployment.
日本語の概要は準備中です。原文の説明を表示しています。
Auditing Terraform infrastructure-as-code for security misconfigurations using Checkov, tfsec, Terrascan, and OPA/Rego policies to detect overly permissive IAM policies, public resource exposure, missing encryption, and insecure defaults before cloud deployment.
日本語の概要は準備中です。原文の説明を表示しています。
InfraGlue (ig) — CLI tool for managing Infrastructure as Code (IaC) monorepos. Orchestrates Terraform and Pulumi workspaces with dependency resolution, output injection, environment management, drift detection, and state reconciliation. Use this skill when working with ig.yaml configs, ig CLI commands, or multi-workspace Terraform/Pulumi infrastructure projects. Keywords: terraform, pulumi, infrastructure, IaC, monorepo, workspace, ig, infraglue, drift, plan, apply, destroy, import, export, refresh, environment.
日本語の概要は準備中です。原文の説明を表示しています。
Build reusable Terraform modules for AWS, Azure, GCP, and OCI infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
日本語の概要は準備中です。原文の説明を表示しています。
Import existing Azure resources into Terraform using Azure CLI discovery and Azure Verified Modules (AVM). Use when asked to reverse-engineer live Azure infrastructure, generate Infrastructure as Code from existing subscriptions/resource groups/resource IDs, map dependencies, derive exact import addresses from downloaded module source, prevent configuration drift, and produce AVM-based Terraform files ready for validation and planning across any Azure resource type.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Terraform or OpenTofu - creating modules, writing tests (native test framework, Terratest), setting up CI/CD pipelines, reviewing configurations, choosing between testing approaches, debugging state issues, implementing security scanning (trivy, checkov), or making infrastructure-as-code architecture decisions
日本語の概要は準備中です。原文の説明を表示しています。
Configures alerting policies in Terraform for Google Kubernetes Engine (GKE) clusters, workloads, and services using PromQL and Google Cloud Managed Service for Prometheus. Use when writing, analyzing, validating, or deploying Terraform alerting policies to monitor GKE service latency, traffic, error rates using Multi-Window Multi-Burn-Rate SLO alerts, memory saturation, and cluster health such as CrashLoopBackOff and Node NotReady conditions. Don't use for non-GKE compute runtimes such as standalone Compute Engine VMs or standalone Cloud Run services without GKE.
日本語の概要は準備中です。原文の説明を表示しています。
Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting deployment failures. Boundaries: - Only use for GCP-specific cloud infrastructure. - Only use for Terraform coding within the ADC context.
日本語の概要は準備中です。原文の説明を表示しています。
Terraform IaC expert for providers, modules, state management, and planning
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development (create reusable modules, manage module versioning), state management (migrate backends, import existing resources, resolve state conflicts), provider configuration, multi-environment workflows, and infrastructure testing.
日本語の概要は準備中です。原文の説明を表示しています。
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD pipelines, containerizing applications, managing infrastructure as code, deploying to Kubernetes clusters, configuring cloud platforms, automating releases, or responding to production incidents. Invoke for pipelines, Docker, Kubernetes, GitOps, Terraform, GitHub Actions, on-call, or platform engineering.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
日本語の概要は準備中です。原文の説明を表示しています。