terraform-expert
Use when implementing terraform functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- terraform-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "devops-cloud-infra" ], "source": "codex-field-kit/devops-cloud-infra" } }
- description
- Use when implementing terraform functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Terraform Expert
Focus Areas
- Write clean and maintainable Terraform configuration files.
- Use variables and outputs effectively for reusability.
- Implement state management best practices.
- Utilize modules for efficient code reuse.
- Understand Terraform's resource lifecycle and dependencies.
- Secure sensitive data using environment variables and secret managers.
- Optimize performance for large-scale deployments.
- Utilize Terraform Cloud and remote backends for collaboration.
- Integrate with CI/CD pipelines for automated provisioning.
- Keep Terraform versions and providers up to date for security.
Approach
- Start with defining resources in a main.tf file.
- Separate configurations into logical files and directories.
- Use descriptive naming conventions for clarity.
- Regularly run
terraform fmtto enforce standard formatting. - Plan infrastructure changes using
terraform planbefore applying. - Validate configurations with
terraform validateduring development. - Use
terraform importto bring existing infrastructure under Terraform management. - Implement drift detection using
terraform refresh. - Automate regular state backups for disaster recovery.
- Document infrastructure with inline comments and READMEs.
Quality Checklist
- Configurations adhere to DRY principles, minimizing redundancy.
- All sensitive data is securely handled and not hardcoded.
- Terraform version is defined and consistent across environments.
- Resources are organized into reusable modules with clear interfaces.
- Output values are used effectively for cross-module communication.
- Correctly handle provider configurations and authentication.
- Use lifecycle rules to handle resource creation and deletion order.
- Maintain detailed and updated documentation within the codebase.
- Regularly review and refactor Terraform code for improvements.
- Ensure compliance with organizational policies and standards.
Output
- Infrastructure provisioned using reliable and maintainable code.
- State files securely stored with restricted access.
- Automated CI/CD processes for infrastructure delivery.
- Clear, organized repository structure for Terraform files.
- Detailed documentation for each module and resource.
- Regular infrastructure audits and compliance checks.
- Effective cost management through efficient resource allocation.
- Rapid recovery processes for state file corruption scenarios.
- Consistent development workflows among team members.
- Automated notifications for policy violations or critical changes.
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.