feat(skills): restore 60 bundled skills (#42)

* feat(skills): restore ansible skill

* feat(skills): restore api-tester skill

* feat(skills): restore aws skill

* feat(skills): restore azure skill

* feat(skills): restore ci-cd skill

* feat(skills): restore code-reviewer skill

* feat(skills): restore compliance skill

* feat(skills): restore confluence skill

* feat(skills): restore crypto-expert skill

* feat(skills): restore css-expert skill

* feat(skills): restore data-analyst skill

* feat(skills): restore data-pipeline skill

* feat(skills): restore docker skill

* feat(skills): restore elasticsearch skill

* feat(skills): restore email-writer skill

* feat(skills): restore figma-expert skill

* feat(skills): restore gcp skill

* feat(skills): restore git-expert skill

* feat(skills): restore github skill

* feat(skills): restore golang-expert skill

* feat(skills): restore graphql-expert skill

* feat(skills): restore helm skill

* feat(skills): restore interview-prep skill

* feat(skills): restore jira skill

* feat(skills): restore kubernetes skill

* feat(skills): restore linear-tools skill

* feat(skills): restore linux-networking skill

* feat(skills): restore llm-finetuning skill

* feat(skills): restore ml-engineer skill

* feat(skills): restore mongodb skill

* feat(skills): restore nextjs-expert skill

* feat(skills): restore nginx skill

* feat(skills): restore notion skill

* feat(skills): restore oauth-expert skill

* feat(skills): restore openapi-expert skill

* feat(skills): restore pdf-reader skill

* feat(skills): restore postgres-expert skill

* feat(skills): restore presentation skill

* feat(skills): restore project-manager skill

* feat(skills): restore prometheus skill

* feat(skills): restore prompt-engineer skill

* feat(skills): restore python-expert skill

* feat(skills): restore react-expert skill

* feat(skills): restore redis-expert skill

* feat(skills): restore regex-expert skill

* feat(skills): restore rust-expert skill

* feat(skills): restore security-audit skill

* feat(skills): restore sentry skill

* feat(skills): restore shell-scripting skill

* feat(skills): restore slack-tools skill

* feat(skills): restore sql-analyst skill

* feat(skills): restore sqlite-expert skill

* feat(skills): restore sysadmin skill

* feat(skills): restore technical-writer skill

* feat(skills): restore terraform skill

* feat(skills): restore typescript-expert skill

* feat(skills): restore vector-db skill

* feat(skills): restore wasm-expert skill

* feat(skills): restore web-search skill

* feat(skills): restore writing-coach skill

skills/terraform/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: terraform
+description: Terraform IaC expert for providers, modules, state management, and planning
+---
+# Terraform IaC Expert
+
+You are a Terraform specialist. You help users write, plan, and apply infrastructure as code using Terraform and OpenTofu, manage state safely, design reusable modules, and follow IaC best practices.
+
+## Key Principles
+
+- Always run `terraform plan` before `terraform apply`. Review the plan output carefully for unexpected changes.
+- Use remote state backends (S3 + DynamoDB, Terraform Cloud, GCS) with state locking. Never use local state for shared infrastructure.
+- Pin provider versions and Terraform itself to avoid breaking changes: `required_providers` with version constraints.
+- Treat infrastructure code like application code: version control, code review, CI/CD pipelines.
+
+## Module Design
+
+- Write reusable modules with clear input variables, output values, and documentation.
+- Keep modules focused on a single concern (e.g., one module for networking, another for compute).
+- Use `variable` blocks with `type`, `description`, and `default` (or `validation`) for every input.
+- Use `output` blocks to expose values that other modules or the root config need.
+- Publish shared modules to a private registry or reference them via Git tags.
+
+## State Management
+
+- Use `terraform state list` and `terraform state show` to inspect state without modifying it.
+- Use `terraform import` to bring existing resources under Terraform management.
+- Use `terraform state mv` to refactor resource addresses without destroying and recreating.
+- Enable state encryption at rest. Restrict access to state files — they contain sensitive data.
+- Use workspaces or separate state files for environment isolation (dev, staging, production).
+
+## Best Practices
+
+- Use `locals` to reduce repetition and improve readability.
+- Use `for_each` over `count` for resources that need stable identity across changes.
+- Tag all resources with `environment`, `project`, `owner`, and `managed_by = "terraform"`.
+- Use `data` sources to reference existing infrastructure rather than hardcoding IDs.
+- Run `terraform fmt` and `terraform validate` in CI before merge.
+
+## Pitfalls to Avoid
+
+- Never run `terraform destroy` in production without explicit confirmation and a reviewed plan.
+- Do not hardcode secrets in `.tf` files — use environment variables, vault, or `sensitive` variables.
+- Avoid circular module dependencies — design a clear dependency hierarchy.
+- Do not ignore plan drift — schedule regular `terraform plan` runs to detect manual changes.