[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78CXDB7KC6NZ3THM5H2QTX2":3,"skill-same:01M78CXDB7KC6NZ3THM5H2QTX2":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":13,"repositoryHtmlUrl":35,"repositoryHomepageUrl":36,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M78CXDB7KC6NZ3THM5H2QTX2","terraform-engineer",null,"Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development (create reusable modules, manage module versioning), state management (migrate backends, import existing resources, resolve state conflicts), provider configuration, multi-environment workflows, and infrastructure testing.","projectweb738-dev\u002FBANKDATA_JHON","projectweb738-dev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F321402929?v=4","01M78BF0E5DXCH964FKTRKZDBT","01M78BF0F66D1WXYXVN7CN29DH",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fterraform-engineer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: terraform-engineer\ndescription: Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development (create reusable modules, manage module versioning), state management (migrate backends, import existing resources, resolve state conflicts), provider configuration, multi-environment workflows, and infrastructure testing.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: infrastructure\n  triggers: Terraform, infrastructure as code, IaC, terraform module, terraform state, AWS provider, Azure provider, GCP provider, terraform plan, terraform apply\n  role: specialist\n  scope: implementation\n  output-format: code\n  related-skills: cloud-architect, devops-engineer, kubernetes-specialist\n---\n\n# Terraform Engineer\n\nSenior Terraform engineer specializing in infrastructure as code across AWS, Azure, and GCP with expertise in modular design, state management, and production-grade patterns.\n\n## Core Workflow\n\n1. **Analyze infrastructure** — Review requirements, existing code, cloud platforms\n2. **Design modules** — Create composable, validated modules with clear interfaces\n3. **Implement state** — Configure remote backends with locking and encryption\n4. **Secure infrastructure** — Apply security policies, least privilege, encryption\n5. **Validate** — Run `terraform fmt` and `terraform validate`, then `tflint`; if any errors are reported, fix them and re-run until all checks pass cleanly before proceeding\n6. **Plan and apply** — Run `terraform plan -out=tfplan`, review output carefully, then `terraform apply tfplan`; if the plan fails, see error recovery below\n\n### Error Recovery\n\n**Validation failures (step 5):** Fix reported errors → re-run `terraform validate` → repeat until clean. For `tflint` warnings, address rule violations before proceeding.\n\n**Plan failures (step 6):**\n- *State drift* — Run `terraform refresh` to reconcile state with real resources, or use `terraform state rm` \u002F `terraform import` to realign specific resources, then re-plan.\n- *Provider auth errors* — Verify credentials, environment variables, and provider configuration blocks; re-run `terraform init` if provider plugins are stale, then re-plan.\n- *Dependency \u002F ordering errors* — Add explicit `depends_on` references or restructure module outputs to resolve unknown values, then re-plan.\n\nAfter any fix, return to step 5 to re-validate before re-running the plan.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Modules | `references\u002Fmodule-patterns.md` | Creating modules, inputs\u002Foutputs, versioning |\n| State | `references\u002Fstate-management.md` | Remote backends, locking, workspaces, migrations |\n| Providers | `references\u002Fproviders.md` | AWS\u002FAzure\u002FGCP configuration, authentication |\n| Testing | `references\u002Ftesting.md` | terraform plan, terratest, policy as code |\n| Best Practices | `references\u002Fbest-practices.md` | DRY patterns, naming, security, cost tracking |\n\n## Constraints\n\n### MUST DO\n- Use semantic versioning and pin provider versions\n- Enable remote state with locking and encryption\n- Validate inputs with validation blocks\n- Use consistent naming conventions and tag all resources\n- Document module interfaces\n- Run `terraform fmt` and `terraform validate`\n\n### MUST NOT DO\n- Store secrets in plain text or hardcode environment-specific values\n- Use local state for production or skip state locking\n- Mix provider versions without constraints\n- Create circular module dependencies or skip input validation\n- Commit `.terraform` directories\n\n## Code Examples\n\n### Minimal Module Structure\n\n**`main.tf`**\n```hcl\nresource \"aws_s3_bucket\" \"this\" {\n  bucket = var.bucket_name\n  tags   = var.tags\n}\n```\n\n**`variables.tf`**\n```hcl\nvariable \"bucket_name\" {\n  description = \"Name of the S3 bucket\"\n  type        = string\n\n  validation {\n    condition     = length(var.bucket_name) > 3\n    error_message = \"bucket_name must be longer than 3 characters.\"\n  }\n}\n\nvariable \"tags\" {\n  description = \"Tags to apply to all resources\"\n  type        = map(string)\n  default     = {}\n}\n```\n\n**`outputs.tf`**\n```hcl\noutput \"bucket_id\" {\n  description = \"ID of the created S3 bucket\"\n  value       = aws_s3_bucket.this.id\n}\n```\n\n### Remote Backend Configuration (S3 + DynamoDB)\n\n```hcl\nterraform {\n  backend \"s3\" {\n    bucket         = \"my-tf-state\"\n    key            = \"env\u002Fprod\u002Fterraform.tfstate\"\n    region         = \"us-east-1\"\n    encrypt        = true\n    dynamodb_table = \"terraform-lock\"\n  }\n}\n```\n\n### Provider Version Pinning\n\n```hcl\nterraform {\n  required_version = \">= 1.5.0\"\n\n  required_providers {\n    aws = {\n      source  = \"hashicorp\u002Faws\"\n      version = \"~> 5.0\"\n    }\n    azurerm = {\n      source  = \"hashicorp\u002Fazurerm\"\n      version = \"~> 3.0\"\n    }\n  }\n}\n```\n\n## Output Format\n\nWhen implementing Terraform solutions, provide: module structure (`main.tf`, `variables.tf`, `outputs.tf`), backend and provider configuration, example usage with tfvars, and a brief explanation of design decisions.\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Finfrastructure\u002Fterraform-engineer\u002F)\n","# Terraform Engineer\n\nSenior Terraform engineer specializing in infrastructure as code across AWS, Azure, and GCP with expertise in modular design, state management, and production-grade patterns.\n\n## Core Workflow\n\n1. **Analyze infrastructure** — Review requirements, existing code, cloud platforms\n2. **Design modules** — Create composable, validated modules with clear interfaces\n3. **Implement state** — Configure remote backends with locking and encryption\n4. **Secure infrastructure** — Apply security policies, least privilege, encryption\n5. **Validate** — Run `terraform fmt` and `terraform validate`, then `tflint`; if any errors are reported, fix them and re-run until all checks pass cleanly before proceeding\n6. **Plan and apply** — Run `terraform plan -out=tfplan`, review output carefully, then `terraform apply tfplan`; if the plan fails, see error recovery below\n\n### Error Recovery\n\n**Validation failures (step 5):** Fix reported errors → re-run `terraform validate` → repeat until clean. For `tflint` warnings, address rule violations before proceeding.\n\n**Plan failures (step 6):**\n- *State drift* — Run `terraform refresh` to reconcile state with real resources, or use `terraform state rm` \u002F `terraform import` to realign specific resources, then re-plan.\n- *Provider auth errors* — Verify credentials, environment variables, and provider configuration blocks; re-run `terraform init` if provider plugins are stale, then re-plan.\n- *Dependency \u002F ordering errors* — Add explicit `depends_on` references or restructure module outputs to resolve unknown values, then re-plan.\n\nAfter any fix, return to step 5 to re-validate before re-running the plan.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Modules | `references\u002Fmodule-patterns.md` | Creating modules, inputs\u002Foutputs, versioning |\n| State | `references\u002Fstate-management.md` | Remote backends, locking, workspaces, migrations |\n| Providers | `references\u002Fproviders.md` | AWS\u002FAzure\u002FGCP configuration, authentication |\n| Testing | `references\u002Ftesting.md` | terraform plan, terratest, policy as code |\n| Best Practices | `references\u002Fbest-practices.md` | DRY patterns, naming, security, cost tracking |\n\n## Constraints\n\n### MUST DO\n- Use semantic versioning and pin provider versions\n- Enable remote state with locking and encryption\n- Validate inputs with validation blocks\n- Use consistent naming conventions and tag all resources\n- Document module interfaces\n- Run `terraform fmt` and `terraform validate`\n\n### MUST NOT DO\n- Store secrets in plain text or hardcode environment-specific values\n- Use local state for production or skip state locking\n- Mix provider versions without constraints\n- Create circular module dependencies or skip input validation\n- Commit `.terraform` directories\n\n## Code Examples\n\n### Minimal Module Structure\n\n**`main.tf`**\n```hcl\nresource \"aws_s3_bucket\" \"this\" {\n  bucket = var.bucket_name\n  tags   = var.tags\n}\n```\n\n**`variables.tf`**\n```hcl\nvariable \"bucket_name\" {\n  description = \"Name of the S3 bucket\"\n  type        = string\n\n  validation {\n    condition     = length(var.bucket_name) > 3\n    error_message = \"bucket_name must be longer than 3 characters.\"\n  }\n}\n\nvariable \"tags\" {\n  description = \"Tags to apply to all resources\"\n  type        = map(string)\n  default     = {}\n}\n```\n\n**`outputs.tf`**\n```hcl\noutput \"bucket_id\" {\n  description = \"ID of the created S3 bucket\"\n  value       = aws_s3_bucket.this.id\n}\n```\n\n### Remote Backend Configuration (S3 + DynamoDB)\n\n```hcl\nterraform {\n  backend \"s3\" {\n    bucket         = \"my-tf-state\"\n    key            = \"env\u002Fprod\u002Fterraform.tfstate\"\n    region         = \"us-east-1\"\n    encrypt        = true\n    dynamodb_table = \"terraform-lock\"\n  }\n}\n```\n\n### Provider Version Pinning\n\n```hcl\nterraform {\n  required_version = \">= 1.5.0\"\n\n  required_providers {\n    aws = {\n      source  = \"hashicorp\u002Faws\"\n      version = \"~> 5.0\"\n    }\n    azurerm = {\n      source  = \"hashicorp\u002Fazurerm\"\n      version = \"~> 3.0\"\n    }\n  }\n}\n```\n\n## Output Format\n\nWhen implementing Terraform solutions, provide: module structure (`main.tf`, `variables.tf`, `outputs.tf`), backend and provider configuration, example usage with tfvars, and a brief explanation of design decisions.\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Finfrastructure\u002Fterraform-engineer\u002F)\n",{"name":5,"license":14,"metadata":23,"description":7},{"role":24,"scope":25,"author":26,"domain":27,"version":28,"triggers":29,"output-format":30,"related-skills":31},"specialist","implementation","https:\u002F\u002Fgithub.com\u002FJeffallan","infrastructure","1.1.0","Terraform, infrastructure as code, IaC, terraform module, terraform state, AWS provider, Azure provider, GCP provider, terraform plan, terraform apply","code","cloud-architect, devops-engineer, kubernetes-specialist","main","1d1992f15739dafb1e105b9293d9d4a60f3f940f","bankdata\u002F.agents\u002Fskills\u002Fterraform-engineer","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON","https:\u002F\u002Fbankdata-jhon.vercel.app","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev","2026-09-01 19:20:34",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add projectweb738-dev\u002FBANKDATA_JHON --skill terraform-engineer",{"tool":45,"command":46},"bunx","bunx skills add projectweb738-dev\u002FBANKDATA_JHON --skill terraform-engineer",{"tool":48,"command":49},"pnpm","pnpm dlx skills add projectweb738-dev\u002FBANKDATA_JHON --skill terraform-engineer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fterraform-engineer\u002FSKILL.md",true,[53,59,63,67,71],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fbest-practices.md","REFERENCE","参考文档",12560,"https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fterraform-engineer\u002Freferences\u002Fbest-practices.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fmodule-patterns.md",5900,"https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fterraform-engineer\u002Freferences\u002Fmodule-patterns.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fproviders.md",9121,"https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fterraform-engineer\u002Freferences\u002Fproviders.md",{"path":68,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fstate-management.md",7913,"https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fterraform-engineer\u002Freferences\u002Fstate-management.md",{"path":72,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Ftesting.md",9816,"https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fterraform-engineer\u002Freferences\u002Ftesting.md",[76,83,90,99,106,114],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M78D1BKYFY69R04PNRR5HSZJ","wordpress-pro","Develops custom WordPress themes and plugins, creates and registers Gutenberg blocks and block patterns, configures WooCommerce stores, implements WordPress REST API endpoints, applies security hardening (nonces, sanitization, escaping, capability checks), and optimizes performance through caching and query tuning. Use when building WordPress themes, writing plugins, customizing Gutenberg blocks, extending WooCommerce, working with ACF, using the WordPress REST API, applying hooks and filters, or improving WordPress performance and security.","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fwordpress-pro\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M78D13G4YF5N0SPXAJRA1JYT","websocket-engineer","Use when building real-time communication systems with WebSockets or Socket.IO. Invoke for bidirectional messaging, horizontal scaling with Redis, presence tracking, room management.","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fwebsocket-engineer\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":94,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M78D10XEZAMYSSWTRE2WS9KK","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":18},"01M78D0V06RFFQBT70678K5Y7M","web-design-guidelines","UI\u002FUX best practices and accessibility audit. Use when reviewing UI code, checking accessibility, running accessibility audits, auditing forms, or ensuring web interface best practices. Triggers on \"audit accessibility\", \"check WCAG\", \"review UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check best practices\".","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":94,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":18},"01M78D0QH26WXXHZW4V54HS0TS","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":18},"01M78D0C3NRETBTGVCFTXG6PSF","vue-expert","Builds Vue 3 components with Composition API patterns, configures Nuxt 3 SSR\u002FSSG projects, sets up Pinia stores, scaffolds Quasar\u002FCapacitor mobile apps, implements PWA features, and optimises Vite builds. Use when creating Vue 3 applications with Composition API, writing reusable composables, managing state with Pinia, building hybrid mobile apps with Quasar or Capacitor, configuring service workers, or tuning Vite configuration and TypeScript integration.","https:\u002F\u002Fgithub.com\u002Fprojectweb738-dev\u002FBANKDATA_JHON\u002Fblob\u002Fmain\u002Fbankdata\u002F.agents\u002Fskills\u002Fvue-expert\u002FSKILL.md",[],[]]