メニュー
Manage infrastructure with version-controlled, reviewed, and tested IaC
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Build UIs that work for all users including keyboard navigation, screen readers, and WCAG 2.2
Design multi-agent systems with robust tool interfaces, state management, and failure handling
Build ML systems with disciplined training, evaluation, deployment, and safety practices
Design APIs that are stable, ergonomic, and evolvable
Design systems at the right scale with explicit trade-off documentation
Design services that are reliable, observable, secure, and maintainable
| name | infrastructure-as-code |
| description | Manage infrastructure with version-controlled, reviewed, and tested IaC |
| difficulty | senior |
| domains | ["infrastructure"] |
Infrastructure defined by hand is infrastructure that drifts, that can't be reviewed, and that can't be reproduced. This skill enforces that all infrastructure is version-controlled code with the same discipline as application code: specs, reviews, tests, and staged deployment.
Write the IaC code that represents the desired state before applying it. Terraform plan / Pulumi preview / CloudFormation change set must be reviewed before apply.
The plan is the diff for infrastructure changes. Review it as carefully as a code diff:
Before applying:
High blast radius changes require explicit approval from a second engineer.
Run drift detection on a schedule. If the actual state diverges from the IaC state, investigate and resolve — don't let drift accumulate.
Apply to: development → staging → production. Wait for validation at each stage before proceeding.
"It's a small change — I'll do it in the console" Console changes become invisible drift. IaC is the only source of truth. No exceptions.
"We don't need to test infrastructure" Untested IaC fails at the worst moment: during an incident when you need to provision fast.
