[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M792GTNJ6MMX9YCPCSGVB60Y":3,"skill-same:01M792GTNJ6MMX9YCPCSGVB60Y":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M792GTNJ6MMX9YCPCSGVB60Y","infrastructure",null,"Write Terraform, Pulumi or CloudFormation and automate provisioning, state and drift detection. Use when writing Terraform, OpenTofu, Pulumi, or cloud IaC manifests.","poorvith-mp\u002Fskills-developer","poorvith-mp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F277478855?v=4","01M78Z5K0YH1Z3PX815PGQ96ND","Poorvith M P","01M792ACSFXT45RJ69SSGKTVJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Finfrastructure\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: infrastructure\nlast_reviewed: 2026-09-06\ngroup: Ship and run\ndescription: >-\n  Write Terraform, Pulumi or CloudFormation and automate provisioning, state and drift detection.\n  Use when writing Terraform, OpenTofu, Pulumi, or cloud IaC manifests.\n---\n\n# Infrastructure\n\nInfrastructure code has a different failure mode than application code: a mistake doesn't just break a test, it can provision the wrong resources, leave something publicly exposed, or rack up unexpected cloud spend. Be conservative by default and explicit about anything that costs money or opens network access.\n\n## Deciding which tool fits\n\n- **Dockerfile \u002F docker-compose** — for containerizing a single app or a small multi-service local dev setup. This is almost always the right starting point even if the user's end goal is Kubernetes — a working Dockerfile is a prerequisite either way.\n- **Terraform** — for provisioning cloud resources themselves (VMs, managed databases, networking, IAM) rather than what runs on top of them. Use when the user is standing up infra, not just packaging an app.\n- **Kubernetes manifests \u002F Helm** — for orchestrating already-containerized apps at a scale or complexity where docker-compose stops being enough (multiple replicas, rolling updates, service discovery across many services). Don't reach for K8s by default for a simple app — it's meaningfully more operational overhead, and it's worth saying so if the user's actual need looks like it fits in docker-compose.\n\n## Dockerfile principles\n\n1. **Multi-stage builds** for compiled\u002Fbundled languages — build in one stage, copy only the artifact into a slim runtime image. This keeps the final image small and avoids shipping build tools into production.\n2. **Pin base image versions** (`node:20-slim`, not `node:latest`) — floating tags mean the same Dockerfile can produce a different image next month, which is exactly the kind of surprise IaC is supposed to prevent.\n3. **Order layers by change frequency** — copy dependency manifests and install dependencies before copying application source, so Docker's layer cache isn't invalidated by every code change.\n4. **Run as a non-root user** in the final image unless there's a specific reason not to — flag this explicitly if generating a Dockerfile that doesn't do it, since running as root is a common and avoidable security gap.\n\n## Terraform principles\n\n1. **State matters more than the config itself.** Always ask (or check for existing config) whether remote state (S3+DynamoDB, Terraform Cloud, etc.) is set up before writing resources — local state is fine for a quick experiment but is a real risk for anything touching shared infrastructure.\n2. **Never hardcode secrets or credentials** in `.tf` files — use variables sourced from environment variables or a secrets manager, and remind the user `.tfvars` files with real secrets shouldn't be committed.\n3. **Default to least-privilege IAM** — don't write a wildcard `*` resource\u002Faction policy just because it's simpler; scope permissions to what the specific resource actually needs.\n4. **Flag anything that costs money or opens public access** before presenting it — e.g. \"this creates an RDS instance, which has an ongoing cost\" or \"this security group rule opens port 22 to 0.0.0.0\u002F0, which exposes SSH to the entire internet — did you mean to scope this to your IP instead?\"\n\n## Kubernetes principles\n\n1. **Set resource requests\u002Flimits** on every container — an unbounded pod can starve its neighbors on the same node, and this is one of the most common things people forget when hand-writing manifests.\n2. **Use a Deployment, not a bare Pod**, for anything that should self-heal or scale — bare Pods don't restart if they crash.\n3. **Liveness\u002Freadiness probes** should be included for anything serving traffic, so Kubernetes actually knows when a pod is unhealthy rather than routing traffic to a broken instance.\n4. **Namespace scoping** — don't default everything to the `default` namespace for a real (non-toy) deployment; ask or infer an appropriate namespace.\n\n## Anti-Patterns & Constraints\n\n- Don't provision real cloud resources yourself (i.e. don't run `terraform apply` or `kubectl apply` against a live cluster) unless the user has explicitly asked you to and confirmed they understand what will be created and its cost — writing the config and applying it are different levels of consequence, treat them that way.\n- Don't silently choose a cloud provider or region — ask if it's not stated or inferable from existing config.\n\n## Output format\n\nProvide the complete file(s), ready to save at the conventional path (`Dockerfile`, `docker-compose.yml`, `main.tf`, `deployment.yaml`), with inline comments on anything non-obvious or anything that costs money\u002Fopens access. Follow with a short plain-language summary of what it provisions and any cost or security flags — before the user applies it, not after.\n\nSee `references\u002Fdockerfile-patterns.md` and `references\u002Fterraform-k8s-patterns.md` for fuller examples per stack.\n\n## Verification & Quality Checklist\n\n- [ ] Code compiles and all automated tests and typechecks pass without new warnings.\n- [ ] Edge cases, boundary conditions, and error states handled explicitly rather than assumed.\n- [ ] No hardcoded secrets, credentials, or insecure defaults introduced.\n- [ ] Changes are covered by a test that fails without them.\n","# Infrastructure\n\nInfrastructure code has a different failure mode than application code: a mistake doesn't just break a test, it can provision the wrong resources, leave something publicly exposed, or rack up unexpected cloud spend. Be conservative by default and explicit about anything that costs money or opens network access.\n\n## Deciding which tool fits\n\n- **Dockerfile \u002F docker-compose** — for containerizing a single app or a small multi-service local dev setup. This is almost always the right starting point even if the user's end goal is Kubernetes — a working Dockerfile is a prerequisite either way.\n- **Terraform** — for provisioning cloud resources themselves (VMs, managed databases, networking, IAM) rather than what runs on top of them. Use when the user is standing up infra, not just packaging an app.\n- **Kubernetes manifests \u002F Helm** — for orchestrating already-containerized apps at a scale or complexity where docker-compose stops being enough (multiple replicas, rolling updates, service discovery across many services). Don't reach for K8s by default for a simple app — it's meaningfully more operational overhead, and it's worth saying so if the user's actual need looks like it fits in docker-compose.\n\n## Dockerfile principles\n\n1. **Multi-stage builds** for compiled\u002Fbundled languages — build in one stage, copy only the artifact into a slim runtime image. This keeps the final image small and avoids shipping build tools into production.\n2. **Pin base image versions** (`node:20-slim`, not `node:latest`) — floating tags mean the same Dockerfile can produce a different image next month, which is exactly the kind of surprise IaC is supposed to prevent.\n3. **Order layers by change frequency** — copy dependency manifests and install dependencies before copying application source, so Docker's layer cache isn't invalidated by every code change.\n4. **Run as a non-root user** in the final image unless there's a specific reason not to — flag this explicitly if generating a Dockerfile that doesn't do it, since running as root is a common and avoidable security gap.\n\n## Terraform principles\n\n1. **State matters more than the config itself.** Always ask (or check for existing config) whether remote state (S3+DynamoDB, Terraform Cloud, etc.) is set up before writing resources — local state is fine for a quick experiment but is a real risk for anything touching shared infrastructure.\n2. **Never hardcode secrets or credentials** in `.tf` files — use variables sourced from environment variables or a secrets manager, and remind the user `.tfvars` files with real secrets shouldn't be committed.\n3. **Default to least-privilege IAM** — don't write a wildcard `*` resource\u002Faction policy just because it's simpler; scope permissions to what the specific resource actually needs.\n4. **Flag anything that costs money or opens public access** before presenting it — e.g. \"this creates an RDS instance, which has an ongoing cost\" or \"this security group rule opens port 22 to 0.0.0.0\u002F0, which exposes SSH to the entire internet — did you mean to scope this to your IP instead?\"\n\n## Kubernetes principles\n\n1. **Set resource requests\u002Flimits** on every container — an unbounded pod can starve its neighbors on the same node, and this is one of the most common things people forget when hand-writing manifests.\n2. **Use a Deployment, not a bare Pod**, for anything that should self-heal or scale — bare Pods don't restart if they crash.\n3. **Liveness\u002Freadiness probes** should be included for anything serving traffic, so Kubernetes actually knows when a pod is unhealthy rather than routing traffic to a broken instance.\n4. **Namespace scoping** — don't default everything to the `default` namespace for a real (non-toy) deployment; ask or infer an appropriate namespace.\n\n## Anti-Patterns & Constraints\n\n- Don't provision real cloud resources yourself (i.e. don't run `terraform apply` or `kubectl apply` against a live cluster) unless the user has explicitly asked you to and confirmed they understand what will be created and its cost — writing the config and applying it are different levels of consequence, treat them that way.\n- Don't silently choose a cloud provider or region — ask if it's not stated or inferable from existing config.\n\n## Output format\n\nProvide the complete file(s), ready to save at the conventional path (`Dockerfile`, `docker-compose.yml`, `main.tf`, `deployment.yaml`), with inline comments on anything non-obvious or anything that costs money\u002Fopens access. Follow with a short plain-language summary of what it provisions and any cost or security flags — before the user applies it, not after.\n\nSee `references\u002Fdockerfile-patterns.md` and `references\u002Fterraform-k8s-patterns.md` for fuller examples per stack.\n\n## Verification & Quality Checklist\n\n- [ ] Code compiles and all automated tests and typechecks pass without new warnings.\n- [ ] Edge cases, boundary conditions, and error states handled explicitly rather than assumed.\n- [ ] No hardcoded secrets, credentials, or insecure defaults introduced.\n- [ ] Changes are covered by a test that fails without them.\n",{"name":5,"group":24,"description":7,"last_reviewed":25},"Ship and run",1788652800000,"main","f6a053c46d4bf0f779ea766c929b6f6f92c51765","skills\u002Finfrastructure","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskillary","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp","poorvithmp.com","Shipping tools for problems people notice too late.","2026-10-02 21:32:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add poorvith-mp\u002Fskills-developer --skill infrastructure",{"tool":41,"command":42},"bunx","bunx skills add poorvith-mp\u002Fskills-developer --skill infrastructure",{"tool":44,"command":45},"pnpm","pnpm dlx skills add poorvith-mp\u002Fskills-developer --skill infrastructure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Finfrastructure\u002FSKILL.md",true,[49,55,61,65],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"evals\u002Frouting.yaml","REFERENCE","参考文档",882,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Finfrastructure\u002Fevals\u002Frouting.yaml",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"infrastructure.skill","OTHER","其他",5284,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Finfrastructure\u002Finfrastructure.skill",{"path":62,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fdockerfile-patterns.md",1464,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Finfrastructure\u002Freferences\u002Fdockerfile-patterns.md",{"path":66,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fterraform-k8s-patterns.md",1911,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Finfrastructure\u002Freferences\u002Fterraform-k8s-patterns.md",[70,77,84,91,98,105],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M792Q79X14YD94WXEEJY9GCW","workflow-optimizer","Moved to workflow-mapping in skills-agents. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-optimizer\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M792Q387DNC91VKEVM07SJM3","webhooks","Build webhook receivers with signature verification, idempotency, retries and dead letter queues. Use when implementing, verifying, or signing incoming\u002Foutgoing webhooks.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Fwebhooks\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M792PZW0SM71X7V9709ZWHCR","webhook-handler-builder","Moved to webhooks in skills-developer. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Fwebhook-handler-builder\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M792PW7XPB7J9S0QSS52JXZV","voice-ai-integration-engineer","Moved to speech-pipelines in skills-developer. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Fvoice-ai-integration-engineer\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M792PRZ5GSAQ1P2999V9XAJ5","typescript-migrator","Moved to port-code in skills-developer. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Ftypescript-migrator\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M792PQDARKP00V8Z3GYD4QZP","trigger-dev","Moved to trigger-dev in skills-agents. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Ftrigger-dev\u002FSKILL.md",[],[]]