eks-buildlisted

# EKS Build Generate complete, production-ready EKS infrastructure projects. All generated code is `terraform apply`-ready with zero manual fixups. All generated Terraform code MUST follow the conventions from these companion skills: - **terraform-skill** -- resource block ordering, variable conventions, file organization, version constraints ## When to Use - Generating EKS Terraform code from requirements (new project) - Scaffolding EKS infrastructure with air-gapped, proxy, or compliance constraints - Creating ArgoCD GitOps integration for EKS addon management - Implementing two-phase webhook ordering for eks-blueprints-addons - Configuring IRSA or Pod Identity for EKS workloads - Generating ArgoCD ApplicationSets for addon lifecycle - Creating Ralph loop validation configurations for EKS projects - Adding custom addons (Kyverno, Prisma, New Relic) to an EKS project - Choosing between or comparing deployment patterns (full Terraform vs ArgoCD+Terraform vs ArgoCD+ACK/KRO) for an actual build ## Don't Use - Designing EKS architecture from requirements (use `eks-design`) - General Terraform module development or testing (use `terraform-skill`) - EKS cluster reconnaissance or discovery (use `eks-recon`) - EKS operational best practices reference (use `eks-best-practices`) - Amazon ECS builds of any kind (use `ecs-build`) ## Internet Search Requirements This skill generates code from scratch every time. **Always search the internet** for: - **Latest versions** of all a