Devops Iac Engineer
Design Terraform/Kubernetes infrastructure, CI/CD, observability, and DevSecOps patterns for cloud-native solo products.
Overview
DevOps IaC Engineer is an agent skill most often used in Operate (also Build, Ship) that guides Terraform, Kubernetes, CI/CD, observability, and security-first cloud infrastructure.
Install
npx skills add https://github.com/davila7/claude-code-templates --skill devops-iac-engineerWhat is this skill?
- Navigation hub to Terraform, Kubernetes, cloud platforms, CI/CD, observability, security, and templates
- Infrastructure as Code and GitOps as core principles across AWS, Azure, and GCP
- Security-first DevOps and site reliability engineering guidance
- Container orchestration and scalable architecture patterns
- Ready-to-use templates referenced in templates.md
- Seven reference areas: Terraform, Kubernetes, cloud platforms, CI/CD, observability, security, templates
Adoption & trust: 638 installs on skills.sh; 27.8k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are shipping on a cloud provider but lack a coherent IaC, pipeline, and observability baseline.
Who is it for?
Solo founders or tiny teams moving from MVP hosting to maintainable cloud infrastructure and GitOps-style deploys.
Skip if: Pure frontend polish, content SEO, or teams that want a single-click host with no Terraform or cluster concepts.
When should I use this skill?
Building cloud architectures, deploying containerized applications, setting up CI/CD pipelines, or implementing observability and security practices.
What do I get? / Deliverables
You leave with aligned Terraform/Kubernetes/CI/CD and monitoring patterns you can implement in your repo and cloud accounts.
- Architecture and IaC pattern recommendations aligned to reference docs
- CI/CD, observability, and security practice checklists drawn from skill sections
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Operate/infra is the canonical shelf because the skill centers on sustaining production infrastructure, even though it also guides earlier pipeline and cluster design. IaC, GitOps, and SRE guidance map directly to running and evolving infrastructure—not launch SEO or idea research.
Where it fits
Pick a container and IaC layout before wiring your API to managed databases.
Define a CI/CD and security checklist ahead of your first production deploy.
Add observability and incident-friendly logging after traffic grows.
Align metrics and alerts with SRE practices from the observability reference.
How it compares
Curated DevOps reference skill—not a hosted CI runner or a one-off MCP deploy button.
Common Questions / FAQ
Who is devops-iac-engineer for?
Indie builders and small DevOps-minded teams implementing or maintaining cloud infrastructure with Terraform, Kubernetes, and standard CI/CD tooling.
When should I use devops-iac-engineer?
In Build/integrations when designing deployable backends; in Ship/launch when hardening release pipelines; in Operate/infra when scaling, monitoring, or securing production.
Is devops-iac-engineer safe to install?
Treat it as guidance that may suggest shell and cloud API usage in your agent—review the Security Audits panel on this page and never apply IaC to production without your own plan review.
SKILL.md
READMESKILL.md - Devops Iac Engineer
# DevOps IaC Engineer This Skill helps DevOps teams design, implement, and maintain cloud infrastructure using Infrastructure as Code principles. Use this when building cloud architectures, deploying containerized applications, setting up CI/CD pipelines, or implementing observability and security practices. ## Quick Navigation - **Terraform & IaC**: See [terraform.md](reference/terraform.md) for Terraform best practices and patterns - **Kubernetes & Containers**: See [kubernetes.md](reference/kubernetes.md) for container orchestration - **Cloud Platforms**: See [cloud_platforms.md](reference/cloud_platforms.md) for AWS, Azure, GCP guidance - **CI/CD Pipelines**: See [cicd.md](reference/cicd.md) for pipeline design and GitOps - **Observability**: See [observability.md](reference/observability.md) for monitoring and logging - **Security**: See [security.md](reference/security.md) for DevSecOps practices - **Templates & Tools**: See [templates.md](reference/templates.md) for ready-to-use templates ## Core Principles ### Key DevOps Terminology (Consistent Throughout) - **Infrastructure as Code (IaC)**: Managing infrastructure through declarative code files - **GitOps**: Using Git as the single source of truth for infrastructure and applications - **Immutable Infrastructure**: Infrastructure components that are replaced rather than modified - **Service Mesh**: Infrastructure layer for service-to-service communication - **Observability**: Ability to understand system state from external outputs (logs, metrics, traces) - **SLI/SLO/SLA**: Service Level Indicators/Objectives/Agreements for reliability - **RTO/RPO**: Recovery Time Objective/Recovery Point Objective for disaster recovery ### Workflow: Infrastructure Implementation When implementing infrastructure, follow this structured approach: 1. **Understand Requirements** - What is the business need? (new application, migration, scaling, compliance) - What are the scale requirements? (traffic, data, geographic distribution) - What are the constraints? (budget, timeline, regulatory) - What are the dependencies? (existing systems, data sources) 2. **Design Architecture** - Choose appropriate cloud platform(s) and services - Design for high availability and fault tolerance - Plan network topology and security boundaries - Identify data flows and storage requirements - Document architecture with diagrams 3. **Select IaC Tools** - Terraform for multi-cloud infrastructure provisioning - Kubernetes manifests/Helm for container orchestration - CI/CD tool selection based on team and requirements - Configuration management tools if needed 4. **Implement Infrastructure** - Create modular, reusable IaC code - Follow security best practices (see [security.md](reference/security.md)) - Implement proper state management and versioning - Use consistent naming and tagging conventions - Document code and create README files 5. **Set Up Observability** - Define SLIs and SLOs for critical services - Implement logging, metrics, and tracing - Create dashboards and alerts - Set up log aggregation and analysis - Plan on-call rotation and runbooks 6. **Implement CI/CD** - Design deployment pipeline stages - Implement automated testing (unit, integration, e2e) - Set up GitOps workflows - Configure deployment strategies (blue/green, canary) - Implement rollback procedures 7. **Test & Validate** - Run infrastructure tests (security, compliance, cost) - Perform disaster recovery drills - Load testing and performance validation - Security scanning and penetration testing - Document test results and improvements