use-aws-mini-stack-emulator

Étoiles10

Forks3

Mis à jour27 juin 2026 à 19:33

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.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

soulcodex

soulcodex/agentic

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

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 AWS Mini Stack Emulator Skill

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.

Step 1 - Select Emulator Scope

Use emulator-compatibility-matrix.md to decide what is safe to validate locally.

Classify each planned check as:

emulator-suitable
partial confidence only
requires real AWS

Step 2 - Configure Provider and Endpoints for Local Runs

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.

Step 3 - Validate Fast Feedback Cases

Good emulator targets:

syntax and interpolation mistakes
module wiring and basic dependencies
selected resource contract checks where behavior is reliably emulated

Step 4 - Document Gaps and Escalate

Always document unsupported services/behaviors and escalate those tests to real AWS validation before merge.

Step 5 - Keep Scope Boundary Explicit

This skill is for local acceleration only. It does not replace real AWS plan/apply verification for production-impacting infrastructure.

It cannot prove:

production backend locking or state migration behavior
IAM or service semantics that emulators do not model faithfully
reviewed plan artifact and approval parity in CI
final confidence for production-impacting provider/runtime upgrades

Avoid overlap with docker-compose-local-setup: this skill covers Terraform + AWS emulation behavior, not generic multi-service compose orchestration design.

Plus depuis ce dépôt

même dépôt

terraform-infrastructure

soulcodex/agentic

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.

2026-06-2710

create-terraform-module

soulcodex/agentic

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.

2026-06-2710

create-terraform-tests

soulcodex/agentic

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.

2026-06-2710

design-aws-terraform-iac

soulcodex/agentic

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.

2026-06-2710

terraform-risk-playbook

soulcodex/agentic

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.

2026-06-2710

code-review-architecture

soulcodex/agentic

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.

2026-05-3010

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 AWS Mini Stack Emulator Skill

Use local AWS emulation to accelerate Terraform feedback loops where appropriate.

Step 1 - Select Emulator Scope

Use emulator-compatibility-matrix.md to decide what is safe to validate locally.

Classify each planned check as:

emulator-suitable
partial confidence only
requires real AWS

Step 2 - Configure Provider and Endpoints for Local Runs

Step 3 - Validate Fast Feedback Cases

Good emulator targets:

syntax and interpolation mistakes
module wiring and basic dependencies
selected resource contract checks where behavior is reliably emulated

Step 4 - Document Gaps and Escalate

Always document unsupported services/behaviors and escalate those tests to real AWS validation before merge.

Step 5 - Keep Scope Boundary Explicit

This skill is for local acceleration only. It does not replace real AWS plan/apply verification for production-impacting infrastructure.

It cannot prove:

production backend locking or state migration behavior
IAM or service semantics that emulators do not model faithfully
reviewed plan artifact and approval parity in CI
final confidence for production-impacting provider/runtime upgrades

Avoid overlap with docker-compose-local-setup: this skill covers Terraform + AWS emulation behavior, not generic multi-service compose orchestration design.