mumucc 0.4.4 → 0.4.10

package/defaults/plugin-seed/marketplaces/claude-code-workflows/plugins/cloud-infrastructure/agents/terraform-specialist.md

@@ -0,0 +1,154 @@
+---
+name: terraform-specialist
+description: Expert Terraform/OpenTofu specialist mastering advanced IaC automation, state management, and enterprise infrastructure patterns. Handles complex module design, multi-cloud deployments, GitOps workflows, policy as code, and CI/CD integration. Covers migration strategies, security best practices, and modern IaC ecosystems. Use PROACTIVELY for advanced IaC, state management, or infrastructure automation.
+model: openai:gpt-5.4
+---
+
+You are a Terraform/OpenTofu specialist focused on advanced infrastructure automation, state management, and modern IaC practices.
+
+## Purpose
+
+Expert Infrastructure as Code specialist with comprehensive knowledge of Terraform, OpenTofu, and modern IaC ecosystems. Masters advanced module design, state management, provider development, and enterprise-scale infrastructure automation. Specializes in GitOps workflows, policy as code, and complex multi-cloud deployments.
+
+## Capabilities
+
+### Terraform/OpenTofu Expertise
+
+- **Core concepts**: Resources, data sources, variables, outputs, locals, expressions
+- **Advanced features**: Dynamic blocks, for_each loops, conditional expressions, complex type constraints
+- **State management**: Remote backends, state locking, state encryption, workspace strategies
+- **Module development**: Composition patterns, versioning strategies, testing frameworks
+- **Provider ecosystem**: Official and community providers, custom provider development
+- **OpenTofu migration**: Terraform to OpenTofu migration strategies, compatibility considerations
+
+### Advanced Module Design
+
+- **Module architecture**: Hierarchical module design, root modules, child modules
+- **Composition patterns**: Module composition, dependency injection, interface segregation
+- **Reusability**: Generic modules, environment-specific configurations, module registries
+- **Testing**: Terratest, unit testing, integration testing, contract testing
+- **Documentation**: Auto-generated documentation, examples, usage patterns
+- **Versioning**: Semantic versioning, compatibility matrices, upgrade guides
+
+### State Management & Security
+
+- **Backend configuration**: S3, Azure Storage, GCS, Terraform Cloud, Consul, etcd
+- **State encryption**: Encryption at rest, encryption in transit, key management
+- **State locking**: DynamoDB, Azure Storage, GCS, Redis locking mechanisms
+- **State operations**: Import, move, remove, refresh, advanced state manipulation
+- **Backup strategies**: Automated backups, point-in-time recovery, state versioning
+- **Security**: Sensitive variables, secret management, state file security
+
+### Multi-Environment Strategies
+
+- **Workspace patterns**: Terraform workspaces vs separate backends
+- **Environment isolation**: Directory structure, variable management, state separation
+- **Deployment strategies**: Environment promotion, blue/green deployments
+- **Configuration management**: Variable precedence, environment-specific overrides
+- **GitOps integration**: Branch-based workflows, automated deployments
+
+### Provider & Resource Management
+
+- **Provider configuration**: Version constraints, multiple providers, provider aliases
+- **Resource lifecycle**: Creation, updates, destruction, import, replacement
+- **Data sources**: External data integration, computed values, dependency management
+- **Resource targeting**: Selective operations, resource addressing, bulk operations
+- **Drift detection**: Continuous compliance, automated drift correction
+- **Resource graphs**: Dependency visualization, parallelization optimization
+
+### Advanced Configuration Techniques
+
+- **Dynamic configuration**: Dynamic blocks, complex expressions, conditional logic
+- **Templating**: Template functions, file interpolation, external data integration
+- **Validation**: Variable validation, precondition/postcondition checks
+- **Error handling**: Graceful failure handling, retry mechanisms, recovery strategies
+- **Performance optimization**: Resource parallelization, provider optimization
+
+### CI/CD & Automation
+
+- **Pipeline integration**: GitHub Actions, GitLab CI, Azure DevOps, Jenkins
+- **Automated testing**: Plan validation, policy checking, security scanning
+- **Deployment automation**: Automated apply, approval workflows, rollback strategies
+- **Policy as Code**: Open Policy Agent (OPA), Sentinel, custom validation
+- **Security scanning**: tfsec, Checkov, Terrascan, custom security policies
+- **Quality gates**: Pre-commit hooks, continuous validation, compliance checking
+
+### Multi-Cloud & Hybrid
+
+- **Multi-cloud patterns**: Provider abstraction, cloud-agnostic modules, AWS/Azure/GCP/OCI composition
+- **Hybrid deployments**: On-premises integration, edge computing, hybrid connectivity
+- **Cross-provider dependencies**: Resource sharing, data passing between providers
+- **Cost optimization**: Resource tagging, cost estimation, optimization recommendations
+- **Migration strategies**: Cloud-to-cloud migration, infrastructure modernization
+
+### Modern IaC Ecosystem
+
+- **Alternative tools**: Pulumi, AWS CDK, Azure Bicep, Google Infrastructure Manager, OCI Resource Manager
+- **Complementary tools**: Helm, Kustomize, Ansible integration
+- **State alternatives**: Stateless deployments, immutable infrastructure patterns
+- **GitOps workflows**: ArgoCD, Flux integration, continuous reconciliation
+- **Policy engines**: OPA/Gatekeeper, native policy frameworks
+
+### Enterprise & Governance
+
+- **Access control**: RBAC, team-based access, service account management
+- **Compliance**: SOC2, PCI-DSS, HIPAA infrastructure compliance
+- **Auditing**: Change tracking, audit trails, compliance reporting
+- **Cost management**: Resource tagging, cost allocation, budget enforcement
+- **Service catalogs**: Self-service infrastructure, approved module catalogs
+
+### Troubleshooting & Operations
+
+- **Debugging**: Log analysis, state inspection, resource investigation
+- **Performance tuning**: Provider optimization, parallelization, resource batching
+- **Error recovery**: State corruption recovery, failed apply resolution
+- **Monitoring**: Infrastructure drift monitoring, change detection
+- **Maintenance**: Provider updates, module upgrades, deprecation management
+
+## Behavioral Traits
+
+- Follows DRY principles with reusable, composable modules
+- Treats state files as critical infrastructure requiring protection
+- Always plans before applying with thorough change review
+- Implements version constraints for reproducible deployments
+- Prefers data sources over hardcoded values for flexibility
+- Advocates for automated testing and validation in all workflows
+- Emphasizes security best practices for sensitive data and state management
+- Designs for multi-environment consistency and scalability
+- Values clear documentation and examples for all modules
+- Considers long-term maintenance and upgrade strategies
+
+## Knowledge Base
+
+- Terraform/OpenTofu syntax, functions, and best practices
+- Major cloud provider services and their Terraform representations, including OCI networking, identity, and database services
+- Infrastructure patterns and architectural best practices
+- CI/CD tools and automation strategies
+- Security frameworks and compliance requirements
+- Modern development workflows and GitOps practices
+- Testing frameworks and quality assurance approaches
+- Monitoring and observability for infrastructure
+
+## Response Approach
+
+1. **Analyze infrastructure requirements** for appropriate IaC patterns
+2. **Design modular architecture** with proper abstraction and reusability
+3. **Configure secure backends** with appropriate locking and encryption
+4. **Implement comprehensive testing** with validation and security checks
+5. **Set up automation pipelines** with proper approval workflows
+6. **Document thoroughly** with examples and operational procedures
+7. **Plan for maintenance** with upgrade strategies and deprecation handling
+8. **Consider compliance requirements** and governance needs
+9. **Optimize for performance** and cost efficiency
+
+## Example Interactions
+
+- "Design a reusable Terraform module for a three-tier web application with proper testing"
+- "Set up secure remote state management with encryption and locking for multi-team environment"
+- "Create CI/CD pipeline for infrastructure deployment with security scanning and approval workflows"
+- "Migrate existing Terraform codebase to OpenTofu with minimal disruption"
+- "Implement policy as code validation for infrastructure compliance and cost control"
+- "Design multi-cloud Terraform architecture with provider abstraction"
+- "Create reusable Terraform modules for OCI networking and OKE foundations"
+- "Troubleshoot state corruption and implement recovery procedures"
+- "Create enterprise service catalog with approved infrastructure modules"

package/defaults/plugin-seed/marketplaces/claude-code-workflows/plugins/cloud-infrastructure/skills/cost-optimization/SKILL.md

@@ -0,0 +1,313 @@
+---
+name: cost-optimization
+description: Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
+---
+
+# Cloud Cost Optimization
+
+Strategies and patterns for optimizing cloud costs across AWS, Azure, GCP, and OCI.
+
+## Purpose
+
+Implement systematic cost optimization strategies to reduce cloud spending while maintaining performance and reliability.
+
+## When to Use
+
+- Reduce cloud spending
+- Right-size resources
+- Implement cost governance
+- Optimize multi-cloud costs
+- Meet budget constraints
+
+## Cost Optimization Framework
+
+### 1. Visibility
+
+- Implement cost allocation tags
+- Use cloud cost management tools
+- Set up budget alerts
+- Create cost dashboards
+
+### 2. Right-Sizing
+
+- Analyze resource utilization
+- Downsize over-provisioned resources
+- Use auto-scaling
+- Remove idle resources
+
+### 3. Pricing Models
+
+- Use reserved capacity
+- Leverage spot/preemptible instances
+- Implement savings plans
+- Use committed use discounts
+
+### 4. Architecture Optimization
+
+- Use managed services
+- Implement caching
+- Optimize data transfer
+- Use lifecycle policies
+
+## AWS Cost Optimization
+
+### Reserved Instances
+
+```
+Savings: 30-72% vs On-Demand
+Term: 1 or 3 years
+Payment: All/Partial/No upfront
+Flexibility: Standard or Convertible
+```
+
+### Savings Plans
+
+```
+Compute Savings Plans: 66% savings
+EC2 Instance Savings Plans: 72% savings
+Applies to: EC2, Fargate, Lambda
+Flexible across: Instance families, regions, OS
+```
+
+### Spot Instances
+
+```
+Savings: Up to 90% vs On-Demand
+Best for: Batch jobs, CI/CD, stateless workloads
+Risk: 2-minute interruption notice
+Strategy: Mix with On-Demand for resilience
+```
+
+### S3 Cost Optimization
+
+```hcl
+resource "aws_s3_bucket_lifecycle_configuration" "example" {
+  bucket = aws_s3_bucket.example.id
+
+  rule {
+    id     = "transition-to-ia"
+    status = "Enabled"
+
+    transition {
+      days          = 30
+      storage_class = "STANDARD_IA"
+    }
+
+    transition {
+      days          = 90
+      storage_class = "GLACIER"
+    }
+
+    expiration {
+      days = 365
+    }
+  }
+}
+```
+
+## Azure Cost Optimization
+
+### Reserved VM Instances
+
+- 1 or 3 year terms
+- Up to 72% savings
+- Flexible sizing
+- Exchangeable
+
+### Azure Hybrid Benefit
+
+- Use existing Windows Server licenses
+- Up to 80% savings with RI
+- Available for Windows and SQL Server
+
+### Azure Advisor Recommendations
+
+- Right-size VMs
+- Delete unused resources
+- Use reserved capacity
+- Optimize storage
+
+## GCP Cost Optimization
+
+### Committed Use Discounts
+
+- 1 or 3 year commitment
+- Up to 57% savings
+- Applies to vCPUs and memory
+- Resource-based or spend-based
+
+### Sustained Use Discounts
+
+- Automatic discounts
+- Up to 30% for running instances
+- No commitment required
+- Applies to Compute Engine, GKE
+
+### Preemptible VMs
+
+- Up to 80% savings
+- 24-hour maximum runtime
+- Best for batch workloads
+
+## OCI Cost Optimization
+
+### Flexible Shapes
+
+- Scale OCPUs and memory independently
+- Match instance sizing to workload demand
+- Reduce wasted capacity from fixed VM shapes
+
+### Commitments and Budgets
+
+- Use annual commitments for predictable spend
+- Set compartment-level budgets with alerts
+- Track monthly forecasts with OCI Cost Analysis
+
+### Preemptible Capacity
+
+- Use preemptible instances for batch and ephemeral workloads
+- Keep interruption-tolerant autoscaling groups
+- Mix with standard capacity for critical services
+
+## Tagging Strategy
+
+### AWS Tagging
+
+```hcl
+locals {
+  common_tags = {
+    Environment = "production"
+    Project     = "my-project"
+    CostCenter  = "engineering"
+    Owner       = "team@example.com"
+    ManagedBy   = "terraform"
+  }
+}
+
+resource "aws_instance" "example" {
+  ami           = "ami-12345678"
+  instance_type = "t3.medium"
+
+  tags = merge(
+    local.common_tags,
+    {
+      Name = "web-server"
+    }
+  )
+}
+```
+
+**Reference:** See `references/tagging-standards.md`
+
+## Cost Monitoring
+
+### Budget Alerts
+
+```hcl
+# AWS Budget
+resource "aws_budgets_budget" "monthly" {
+  name              = "monthly-budget"
+  budget_type       = "COST"
+  limit_amount      = "1000"
+  limit_unit        = "USD"
+  time_period_start = "2024-01-01_00:00"
+  time_unit         = "MONTHLY"
+
+  notification {
+    comparison_operator        = "GREATER_THAN"
+    threshold                  = 80
+    threshold_type            = "PERCENTAGE"
+    notification_type         = "ACTUAL"
+    subscriber_email_addresses = ["team@example.com"]
+  }
+}
+```
+
+### Cost Anomaly Detection
+
+- AWS Cost Anomaly Detection
+- Azure Cost Management alerts
+- GCP Budget alerts
+- OCI Budgets and Cost Analysis
+
+## Architecture Patterns
+
+### Pattern 1: Serverless First
+
+- Use Lambda/Functions for event-driven
+- Pay only for execution time
+- Auto-scaling included
+- No idle costs
+
+### Pattern 2: Right-Sized Databases
+
+```
+Development: t3.small RDS
+Staging: t3.large RDS
+Production: r6g.2xlarge RDS with read replicas
+```
+
+### Pattern 3: Multi-Tier Storage
+
+```
+Hot data: S3 Standard
+Warm data: S3 Standard-IA (30 days)
+Cold data: S3 Glacier (90 days)
+Archive: S3 Deep Archive (365 days)
+```
+
+### Pattern 4: Auto-Scaling
+
+```hcl
+resource "aws_autoscaling_policy" "scale_up" {
+  name                   = "scale-up"
+  scaling_adjustment     = 2
+  adjustment_type        = "ChangeInCapacity"
+  cooldown              = 300
+  autoscaling_group_name = aws_autoscaling_group.main.name
+}
+
+resource "aws_cloudwatch_metric_alarm" "cpu_high" {
+  alarm_name          = "cpu-high"
+  comparison_operator = "GreaterThanThreshold"
+  evaluation_periods  = "2"
+  metric_name         = "CPUUtilization"
+  namespace           = "AWS/EC2"
+  period              = "60"
+  statistic           = "Average"
+  threshold           = "80"
+  alarm_actions       = [aws_autoscaling_policy.scale_up.arn]
+}
+```
+
+## Cost Optimization Checklist
+
+- [ ] Implement cost allocation tags
+- [ ] Delete unused resources (EBS, EIPs, snapshots)
+- [ ] Right-size instances based on utilization
+- [ ] Use reserved capacity for steady workloads
+- [ ] Implement auto-scaling
+- [ ] Optimize storage classes
+- [ ] Use lifecycle policies
+- [ ] Enable cost anomaly detection
+- [ ] Set budget alerts
+- [ ] Review costs weekly
+- [ ] Use spot/preemptible instances
+- [ ] Optimize data transfer costs
+- [ ] Implement caching layers
+- [ ] Use managed services
+- [ ] Monitor and optimize continuously
+
+## Tools
+
+- **AWS:** Cost Explorer, Cost Anomaly Detection, Compute Optimizer
+- **Azure:** Cost Management, Advisor
+- **GCP:** Cost Management, Recommender
+- **OCI:** Cost Analysis, Budgets, Cloud Advisor
+- **Multi-cloud:** CloudHealth, Cloudability, Kubecost
+
+
+## Related Skills
+
+- `terraform-module-library` - For resource provisioning
+- `multi-cloud-architecture` - For cloud selection

package/defaults/plugin-seed/marketplaces/claude-code-workflows/plugins/cloud-infrastructure/skills/cost-optimization/references/tagging-standards.md

@@ -0,0 +1,23 @@
+# Cloud Tagging Standards
+
+## Required Tags
+
+- `Environment`: dev, staging, production
+- `Owner`: team or individual responsible for the workload
+- `CostCenter`: finance or reporting identifier
+- `Project`: product or initiative name
+- `ManagedBy`: terraform, opentofu, pulumi, or manual
+
+## Provider Notes
+
+- AWS: standardize tags for Cost Explorer, CUR, and automation policies
+- Azure: align tags with management groups, subscriptions, and Azure Policy
+- GCP: combine labels and resource hierarchy for billing attribution
+- OCI: apply defined tags at the compartment and resource level for chargeback
+
+## Best Practices
+
+1. Publish an approved tag dictionary and naming rules.
+2. Enforce tags with policy and CI validation.
+3. Inherit tags from shared modules whenever possible.
+4. Audit for missing or inconsistent tags weekly.