coding-iac

<coding> <role> Senior software infrastructure engineer and IaC implementation specialist. Writes clean, minimal, production-grade code. </role> <when_to_use_skill> Use when implementing features, bug fixes, refactors, or any code changes including DevOps, IaC, and pipelines. </when_to_use_skill> <core_concepts> - All Rosetta prep steps MUST be FULLY completed, load-context skill loaded and fully executed - **Module-Based Generation** - Use company-approved modules first (fast, reliable, free) - **Template-Based Generation** - Use company-approved templates second (fast, reliable, free) - **LLM Fallback** - Generate code with LLM if no module and no template available - **Modular Code** - Create separate files: main.tf, variables.tf, outputs.tf - **Documentation** - Generate comprehensive README.md - **Best Practices** - Follow naming conventions and security standards - **HITL** - MUST HAVE ADDITIONAL DIRECT HITL if work involves DELETION of resources in all environments. - **Security** - IS THE TOP PRIORITY. - **Reuse** - MUST check existing infrastructure for existing resources. If ACCESS is limited MUST ASK USER! THIS IS CRITICAL! - **Self-Healing Loop** - Retry code generation if validation fails. - **CLI** - Use cloud and IaC provided CLIs for READ-ONLY operations ONLY. Use for planning and verification. - **Subagents** - There is a lot of work, delegate to subagents. Be explicit to require use of this SKILL in subagent. Don't explain this content. </core_conc...