claude-autopm 2.8.2 → 2.8.4

package/packages/plugin-cloud/commands/cloud-validate.md

@@ -0,0 +1,196 @@
+# cloud:validate
+
+Validate cloud infrastructure configuration and credentials across AWS, Azure, and GCP.
+
+## Description
+
+Performs comprehensive validation of cloud infrastructure setup including:
+- Cloud provider credentials and authentication
+- IAC configuration files (Terraform, CloudFormation, ARM templates)
+- Resource naming conventions and tagging compliance
+- Security best practices and compliance checks
+- Cost optimization opportunities
+
+## Required Documentation Access
+
+**MANDATORY:** Before executing validation, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/aws/best-practices` - AWS Well-Architected Framework
+- `mcp://context7/azure/best-practices` - Azure Cloud Adoption Framework
+- `mcp://context7/gcp/best-practices` - Google Cloud Architecture Framework
+- `mcp://context7/terraform/validation` - Terraform validation and testing patterns
+- `mcp://context7/security/cloud-security` - Cloud security hardening guidelines
+
+**Why This is Required:**
+- Ensures validation follows cloud provider best practices
+- Applies latest security recommendations
+- Validates against current compliance standards
+- Prevents misconfigurations and vulnerabilities
+
+## Usage
+
+```bash
+/cloud:validate [options]
+```
+
+## Options
+
+- `--provider <aws|azure|gcp|all>` - Cloud provider to validate (default: all)
+- `--scope <credentials|config|security|cost|all>` - Validation scope (default: all)
+- `--fix` - Attempt to fix issues automatically
+- `--report <path>` - Generate validation report at specified path
+- `--strict` - Fail on warnings (default: fail on errors only)
+
+## Examples
+
+### Validate All Cloud Providers
+```bash
+/cloud:validate
+```
+
+### Validate AWS Configuration Only
+```bash
+/cloud:validate --provider aws --scope config
+```
+
+### Validate with Auto-Fix
+```bash
+/cloud:validate --provider azure --fix
+```
+
+### Generate Security Validation Report
+```bash
+/cloud:validate --scope security --report ./security-audit.md
+```
+
+## Validation Checks
+
+### Credentials
+- ✅ AWS credentials in ~/.aws/credentials or environment
+- ✅ Azure CLI authentication status
+- ✅ GCP service account or user credentials
+- ✅ Permission scope and access levels
+- ✅ Credential rotation compliance
+
+### Configuration
+- ✅ Terraform/IaC syntax validation
+- ✅ Provider version compatibility
+- ✅ Backend configuration (state management)
+- ✅ Variable definitions and defaults
+- ✅ Module source verification
+
+### Security
+- ✅ Public exposure risks (S3 buckets, security groups)
+- ✅ Encryption at rest and in transit
+- ✅ IAM/RBAC policy compliance
+- ✅ Network security (VPC, NSG, firewall rules)
+- ✅ Secret management practices
+
+### Cost Optimization
+- ✅ Resource sizing recommendations
+- ✅ Unused or underutilized resources
+- ✅ Reserved instance opportunities
+- ✅ Storage class optimization
+- ✅ Network data transfer costs
+
+## Implementation
+
+This command uses specialized cloud agents to perform validation:
+
+1. **@aws-cloud-architect** - AWS validation
+2. **@azure-cloud-architect** - Azure validation
+3. **@gcp-cloud-architect** - GCP validation
+4. **@terraform-infrastructure-expert** - IaC validation
+
+The command:
+1. Queries Context7 for provider-specific best practices
+2. Executes validation scripts for each provider
+3. Aggregates results and generates reports
+4. Optionally applies fixes for common issues
+5. Provides actionable recommendations
+
+## Exit Codes
+
+- `0` - All validations passed
+- `1` - Validation warnings found (fail with --strict)
+- `2` - Validation errors found
+- `3` - Critical security issues found
+- `4` - Configuration errors prevent validation
+
+## Output Format
+
+### Console Output
+```
+☁️  Cloud Infrastructure Validation
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+AWS Validation
+  ✅ Credentials: Valid (us-east-1)
+  ✅ Configuration: 12 resources validated
+  ⚠️  Security: 2 warnings (S3 bucket encryption)
+  ✅ Cost: No optimization opportunities
+
+Azure Validation
+  ✅ Credentials: Valid (subscription: prod-001)
+  ✅ Configuration: 8 resources validated
+  ✅ Security: All checks passed
+  💰 Cost: 3 optimization opportunities found
+
+GCP Validation
+  ✅ Credentials: Valid (project: my-project)
+  ✅ Configuration: 15 resources validated
+  ✅ Security: All checks passed
+  ✅ Cost: No optimization opportunities
+
+Summary
+  Total Resources: 35
+  ✅ Passed: 33
+  ⚠️  Warnings: 2
+  ❌ Errors: 0
+  💰 Cost Savings: ~$120/month
+```
+
+### Report Output (Markdown)
+Generates comprehensive markdown report with:
+- Executive summary
+- Detailed findings by provider
+- Security compliance matrix
+- Cost optimization recommendations
+- Remediation steps with code examples
+
+## Related Commands
+
+- `/cloud:deploy` - Deploy validated infrastructure
+- `/cloud:cost-analysis` - Detailed cost analysis
+- `/cloud:security-scan` - Deep security scanning
+- `/infra-deploy` - Infrastructure deployment
+
+## Best Practices
+
+1. **Run Before Deployment**: Always validate before deploying changes
+2. **CI/CD Integration**: Include in pipeline for automated checks
+3. **Regular Audits**: Schedule weekly validation runs
+4. **Fix Warnings**: Address warnings before they become errors
+5. **Document Exceptions**: Track validation exceptions with justification
+
+## Troubleshooting
+
+### Authentication Failures
+- Verify cloud CLI installation (aws-cli, azure-cli, gcloud)
+- Check credential files and environment variables
+- Ensure proper permissions and access scopes
+
+### Configuration Errors
+- Run `terraform fmt` and `terraform validate`
+- Check provider version compatibility
+- Verify module sources and versions
+
+### Performance Issues
+- Use `--provider` flag to limit scope
+- Run validations in parallel for large infrastructures
+- Cache provider API responses when possible
+
+## Version History
+
+- v2.0.0 - Initial Schema v2.0 release with Context7 integration

package/packages/plugin-cloud/commands/infra-deploy.md

@@ -0,0 +1,38 @@
+---
+allowed-tools: Task, Read, Write, Edit, MultiEdit, Bash, Glob, Grep
+---
+
+# Cloud Infrastructure Deployment
+
+Deploys infrastructure to cloud providers using Terraform.
+
+**Usage**: `/cloud:infra-deploy [--provider=aws|azure|gcp] [--env=dev|staging|prod] [--services=compute,storage,database]`
+
+## Required Documentation Access
+
+**MANDATORY:** Before deploying infrastructure, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/infrastructure/deployment` - deployment best practices
+- `mcp://context7/cloud/best-practices` - best practices best practices
+- `mcp://context7/devops/automation` - automation best practices
+- `mcp://context7/infrastructure/configuration` - configuration best practices
+
+**Why This is Required:**
+- Ensures adherence to current industry standards and best practices
+- Prevents outdated or incorrect implementation patterns
+- Provides access to latest framework/tool documentation
+- Reduces errors from stale knowledge or assumptions
+
+
+**Example**: `/cloud:infra-deploy --provider=aws --env=staging --services=eks,rds,s3`
+
+**What this does**:
+- Creates Terraform modules for selected cloud
+- Configures provider and backend
+- Sets up networking and security
+- Deploys requested services
+- Implements cost optimization
+- Adds monitoring and alerting
+
+Use the appropriate cloud architect agent (aws-cloud-architect, azure-cloud-architect, or gcp-cloud-architect) based on provider.

package/packages/plugin-cloud/commands/k8s-deploy.md

@@ -0,0 +1,37 @@
+---
+allowed-tools: Task, Read, Write, Edit, MultiEdit, Bash, Glob, Grep
+---
+
+# Kubernetes Deployment
+
+Deploys applications to Kubernetes clusters.
+
+**Usage**: `/kubernetes:deploy [app-name] [--chart=helm|kustomize] [--namespace=default] [--gitops=argocd|flux]`
+
+## Required Documentation Access
+
+**MANDATORY:** Before Kubernetes deployment, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/kubernetes/deployment` - deployment best practices
+- `mcp://context7/kubernetes/best-practices` - best practices best practices
+- `mcp://context7/devops/container-orchestration` - container orchestration best practices
+
+**Why This is Required:**
+- Ensures adherence to current industry standards and best practices
+- Prevents outdated or incorrect implementation patterns
+- Provides access to latest framework/tool documentation
+- Reduces errors from stale knowledge or assumptions
+
+
+**Example**: `/kubernetes:deploy my-app --chart=helm --namespace=production --gitops=argocd`
+
+**What this does**:
+- Creates Kubernetes manifests or Helm charts
+- Configures deployments with best practices
+- Sets up services and ingress
+- Implements autoscaling and monitoring
+- Configures GitOps if requested
+- Adds security policies
+
+Use the kubernetes-orchestrator agent to deploy applications to Kubernetes.

package/packages/plugin-cloud/commands/ssh-security.md

@@ -0,0 +1,65 @@
+---
+name: ssh-security-and-operations
+type: epic-management
+category: infrastructure
+---
+
+# SSH Security and Operations Command
+
+Set up secure SSH configurations, key management, and remote operations.
+
+## Command
+```
+/infra:ssh-security
+```
+
+## Purpose
+Use the ssh-operations-expert agent to create secure SSH configurations, implement key rotation strategies, and set up remote management workflows.
+
+## Parameters
+- `scope`: Configuration scope (client, server, both)
+- `security_level`: Security hardening level (basic, advanced, paranoid)
+- `key_management`: Key management strategy (manual, automated, ca-based)
+- `features`: Additional features (tunneling, jump-hosts, automation)
+
+## Agent Usage
+```
+Use the ssh-operations-expert agent to create comprehensive SSH security and operations setup.
+```
+
+## Expected Outcome
+- Hardened SSH client/server configurations
+- SSH key generation and management scripts
+- Automated key rotation workflows
+- Tunnel and port forwarding setup
+- Jump host and bastion configuration
+- Remote operations and automation scripts
+- Security audit and monitoring tools
+
+## Example Usage
+```
+## Required Documentation Access
+
+**MANDATORY:** Before SSH security hardening, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/security/ssh-hardening` - ssh hardening best practices
+- `mcp://context7/security/authentication` - authentication best practices
+- `mcp://context7/infrastructure/security` - security best practices
+- `mcp://context7/security/best-practices` - best practices best practices
+
+**Why This is Required:**
+- Ensures adherence to current industry standards and best practices
+- Prevents outdated or incorrect implementation patterns
+- Provides access to latest framework/tool documentation
+- Reduces errors from stale knowledge or assumptions
+
+
+Task: Set up secure SSH infrastructure with key rotation, jump hosts, and automated remote operations
+Agent: ssh-operations-expert
+Parameters: scope=both, security_level=advanced, key_management=automated, features=tunneling,jump-hosts,automation
+```
+
+## Related Agents
+- bash-scripting-expert: For automation scripts
+- terraform-infrastructure-expert: For infrastructure automation

package/packages/plugin-cloud/commands/traefik-setup.md

@@ -0,0 +1,65 @@
+---
+name: traefik-reverse-proxy-setup
+type: epic-management
+category: infrastructure
+---
+
+# Traefik Reverse Proxy Setup Command
+
+Configure Traefik reverse proxy with SSL termination, load balancing, and service discovery.
+
+## Command
+```
+/infra:traefik-setup
+```
+
+## Purpose
+Use the traefik-proxy-expert agent to create a complete Traefik reverse proxy configuration with SSL automation, load balancing, and microservices routing.
+
+## Parameters
+- `environment`: Target environment (development, staging, production)
+- `ssl`: SSL configuration (letsencrypt, custom-certs, self-signed)
+- `discovery`: Service discovery method (docker, kubernetes, file)
+- `features`: Additional features (dashboard, metrics, rate-limiting, auth)
+
+## Agent Usage
+```
+Use the traefik-proxy-expert agent to create a comprehensive Traefik reverse proxy setup.
+```
+
+## Expected Outcome
+- Complete Traefik configuration (traefik.yml)
+- Docker Compose setup with Traefik service
+- SSL certificate automation
+- Service discovery configuration
+- Load balancing and health checks
+- Security middleware and authentication
+- Monitoring and logging setup
+
+## Example Usage
+```
+## Required Documentation Access
+
+**MANDATORY:** Before Traefik setup, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/infrastructure/reverse-proxy` - reverse proxy best practices
+- `mcp://context7/traefik/configuration` - configuration best practices
+- `mcp://context7/devops/networking` - networking best practices
+- `mcp://context7/security/tls` - tls best practices
+
+**Why This is Required:**
+- Ensures adherence to current industry standards and best practices
+- Prevents outdated or incorrect implementation patterns
+- Provides access to latest framework/tool documentation
+- Reduces errors from stale knowledge or assumptions
+
+
+Task: Set up Traefik reverse proxy for microservices with Let's Encrypt SSL and Docker discovery
+Agent: traefik-proxy-expert
+Parameters: environment=production, ssl=letsencrypt, discovery=docker, features=dashboard,metrics,auth
+```
+
+## Related Agents
+- docker-containerization-expert: For container configuration
+- kubernetes-orchestrator: For K8s integration