メニュー
Generate Infrastructure as Code templates using Terraform, Pulumi, or AWS CDK. Do NOT use for Dockerfile creation, CI/CD pipelines, or application-level configuration.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use to implement a REST or GraphQL API endpoint from a specification or description, including request validation, error handling, and accompanying tests. Activate for building a new API route, resolver, or handler end-to-end. Do NOT use for API design/contract creation, documentation generation, or frontend API consumption.
Use to implement background job processing with a queue, worker, retry with exponential backoff, dead letter queue, and monitoring. Activate when the request involves offloading work from the request cycle (emails, reports, data processing). Do NOT use for real-time event streaming, webhook handling, or scheduled cron jobs.
Use to scaffold a new project from scratch — generating directory structure, configuration files, entry points, and a README skeleton. Activate when starting a new project, service, or package and needing a production-ready starting point. Do NOT use for adding features to existing projects, generating tests, or CI/CD configuration.
Use to design and implement a caching layer for data that is expensive to compute or fetch. Activate for cache-aside, write-through, or write-behind patterns, TTL strategy, and cache invalidation logic. Do NOT use for database query optimization, CDN configuration, or HTTP response caching headers.
Use to generate a CI/CD pipeline configuration for building, testing, and deploying an application. Activate for GitHub Actions, GitLab CI, CircleCI, or similar pipeline tools for any tech stack. Do NOT use for infrastructure provisioning, Dockerfile creation, or deployment strategy design.
Use to generate production-ready code for a new feature, function, class, or module from a description. Activate for writing new code from scratch with error handling, inline documentation, and a self-review checklist. Do NOT use for refactoring existing code, code review, or test generation.
| name | infrastructure-as-code |
| description | Generate Infrastructure as Code templates using Terraform, Pulumi, or AWS CDK. Do NOT use for Dockerfile creation, CI/CD pipelines, or application-level configuration. |
| version | 1.1.0 |
| time_saved | Manual: 4–8 hours | With skill: 30–60 minutes |
| license | Proprietary — Personal Use Only |
| category | coding |
| complexity | Advanced |
| tokens | ~4500 |
| tags | ["terraform","pulumi","cdk","infrastructure-as-code","cloud","devops"] |
| author | vheins |
Generate modular, secure, and production-ready IaC templates (Terraform, Pulumi, CDK).
| Variable | Type | Req | Description |
|---|---|---|---|
tech_stack | string | Yes | Cloud provider + App stack |
iac_tool | string | Yes | e.g., "Terraform", "AWS CDK (Python)" |
infrastructure_requirements | string | Yes | Required resources, network, DB, security |
| Case | Strategy |
|---|---|
| Multi-region | Generate region-instantiable modules; note cross-region state complexity. |
| Existing Infra | Provide terraform import or fromLookup instructions. |
| Cost Control | Suggest cheaper non-prod alternatives (e.g., smaller instances). |
flowchart TD
A([Start: Infrastructure as Code]) --> B[Identify target infrastructure]
B --> C{IaC tool?}
C -- Terraform --> D[Init provider + backend config]
C -- Pulumi --> E[Init stack + language runtime]
C -- CDK --> F[Init app + construct library]
C -- Ansible --> G[Define inventory + playbooks]
D & E & F & G --> H[Define environments: dev / staging / prod]
H --> I{State management?}
I -- Remote --> J[Configure remote state]
I -- Local --> K[Local state - flag for team use]
J & K --> L[Define modules/constructs for reuse]
L --> M[Parameterize: variables, env-specific overrides]
M --> N{Secrets handling?}
N -- Vault / SSM --> O[Reference secrets from store]
N -- Env vars --> P[Inject at runtime via CI/CD]
O & P --> Q[Plan / preview changes]
Q --> R{Drift detected?}
R -- Yes --> S[Reconcile: import existing or adjust code]
R -- No --> T[Apply to dev first, validate]
S --> T
T --> U{Tests pass?}
U -- No --> V[Fix IaC code, re-plan]
U -- Yes --> W[Promote to staging → prod via pipeline]
V --> Q
W --> X[Tag resources]
X --> Y([Output: Versioned, modular IaC])
@upstash/context7-mcp: Library documentation and examples.| Version | Date | Description |
|---|---|---|
| 1.1.0 | 2026-03-20 | Restructured: moved examples/references, added compatibility/license |
| 1.0.0 | 2026-03-20 | Initial release |