القائمة
Uses lightweight AWS stack emulation for faster local Terraform iteration. Defines what can be safely validated locally, compatibility caveats, and the handoff boundary to real-AWS verification and reviewed plan/apply flows.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Structures, writes, and reviews Terraform infrastructure code. Covers module layout, remote state, workspace strategy, variable and secrets handling, CI plan/apply pipeline, naming conventions, and multi-region deployment patterns (provider aliases, per-region state, failover strategies), while delegating shared risk classification, version guards, and rollback contract to `terraform-risk-playbook`. Invoked when the user asks to write Terraform, set up infrastructure as code, or review IaC.
Creates or updates AWS-oriented Terraform module structure and implementation scaffolding. Focuses on file layout, variable/output contracts, provider and version constraints, tagging standards, safe composition patterns, and address-stability guardrails.
Designs and implements Terraform module tests for AWS-targeted modules. Covers terraform-native tests, validation gates, fixture composition, and risk-focused assertions for regressions, address migration, and unsafe changes.
Designs AWS-targeted Terraform infrastructure plans before implementation. Focuses on service selection, module boundaries, state/backends, environment separation, security/compliance guardrails, acceptance criteria, and explicit risk/validation assumptions.
Diagnoses Terraform/OpenTofu risk before generating changes. Defines the response contract, failure-mode routing, version/runtime guards, validation commands, and rollback expectations for modules, tests, CI, and state work.
Architecture-focused code review covering hexagonal boundary violations, DDD anti-patterns, CQRS misuse, and microservices coupling issues. Applied in addition to the language-specific review skill when architecture markers are detected. Invoked when reviewing hexagonal architectures, DDD patterns, or microservices boundaries.
| name | use-aws-mini-stack-emulator |
| description | Uses lightweight AWS stack emulation for faster local Terraform iteration. Defines what can be safely validated locally, compatibility caveats, and the handoff boundary to real-AWS verification and reviewed plan/apply flows. |
| version | 1.1.0 |
| tags | ["devops","terraform","aws","local-testing"] |
| resources | ["emulator-compatibility-matrix.md"] |
| vendor_support | {"claude":"native","opencode":"native","copilot":"prompt-inject","codex":"prompt-inject","gemini":"prompt-inject"} |
Use local AWS emulation to accelerate Terraform feedback loops where appropriate.
Always pair this skill with terraform-risk-playbook. That skill is
authoritative for the response contract, failure-mode classification,
version/runtime guards, validation chain, and rollback notes.
Use emulator-compatibility-matrix.md to decide what is safe to validate locally.
Classify each planned check as:
Keep local endpoint wiring isolated from production configuration. Use explicit
variables or per-environment override files for emulator endpoint settings.
Use local state or terraform init -backend=false for emulator-first CI checks
to avoid touching shared remote backends.
Good emulator targets:
Always document unsupported services/behaviors and escalate those tests to real AWS validation before merge.
This skill is for local acceleration only. It does not replace real AWS plan/apply verification for production-impacting infrastructure.
It cannot prove:
Avoid overlap with docker-compose-local-setup: this skill covers Terraform + AWS
emulation behavior, not generic multi-service compose orchestration design.
