@cubis/foundry 0.3.10

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/skills/deployment-procedures/SKILL.md

@@ -0,0 +1,241 @@
+---
+name: deployment-procedures
+description: Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
+allowed-tools: Read, Glob, Grep, Bash
+---
+
+# Deployment Procedures
+
+> Deployment principles and decision-making for safe production releases.
+> **Learn to THINK, not memorize scripts.**
+
+---
+
+## ⚠️ How to Use This Skill
+
+This skill teaches **deployment principles**, not bash scripts to copy.
+
+- Every deployment is unique
+- Understand the WHY behind each step
+- Adapt procedures to your platform
+
+---
+
+## 1. Platform Selection
+
+### Decision Tree
+
+```
+What are you deploying?
+│
+├── Static site / JAMstack
+│   └── Vercel, Netlify, Cloudflare Pages
+│
+├── Simple web app
+│   ├── Managed → Railway, Render, Fly.io
+│   └── Control → VPS + PM2/Docker
+│
+├── Microservices
+│   └── Container orchestration
+│
+└── Serverless
+    └── Edge functions, Lambda
+```
+
+### Each Platform Has Different Procedures
+
+| Platform | Deployment Method |
+|----------|------------------|
+| **Vercel/Netlify** | Git push, auto-deploy |
+| **Railway/Render** | Git push or CLI |
+| **VPS + PM2** | SSH + manual steps |
+| **Docker** | Image push + orchestration |
+| **Kubernetes** | kubectl apply |
+
+---
+
+## 2. Pre-Deployment Principles
+
+### The 4 Verification Categories
+
+| Category | What to Check |
+|----------|--------------|
+| **Code Quality** | Tests passing, linting clean, reviewed |
+| **Build** | Production build works, no warnings |
+| **Environment** | Env vars set, secrets current |
+| **Safety** | Backup done, rollback plan ready |
+
+### Pre-Deployment Checklist
+
+- [ ] All tests passing
+- [ ] Code reviewed and approved
+- [ ] Production build successful
+- [ ] Environment variables verified
+- [ ] Database migrations ready (if any)
+- [ ] Rollback plan documented
+- [ ] Team notified
+- [ ] Monitoring ready
+
+---
+
+## 3. Deployment Workflow Principles
+
+### The 5-Phase Process
+
+```
+1. PREPARE
+   └── Verify code, build, env vars
+
+2. BACKUP
+   └── Save current state before changing
+
+3. DEPLOY
+   └── Execute with monitoring open
+
+4. VERIFY
+   └── Health check, logs, key flows
+
+5. CONFIRM or ROLLBACK
+   └── All good? Confirm. Issues? Rollback.
+```
+
+### Phase Principles
+
+| Phase | Principle |
+|-------|-----------|
+| **Prepare** | Never deploy untested code |
+| **Backup** | Can't rollback without backup |
+| **Deploy** | Watch it happen, don't walk away |
+| **Verify** | Trust but verify |
+| **Confirm** | Have rollback trigger ready |
+
+---
+
+## 4. Post-Deployment Verification
+
+### What to Verify
+
+| Check | Why |
+|-------|-----|
+| **Health endpoint** | Service is running |
+| **Error logs** | No new errors |
+| **Key user flows** | Critical features work |
+| **Performance** | Response times acceptable |
+
+### Verification Window
+
+- **First 5 minutes**: Active monitoring
+- **15 minutes**: Confirm stable
+- **1 hour**: Final verification
+- **Next day**: Review metrics
+
+---
+
+## 5. Rollback Principles
+
+### When to Rollback
+
+| Symptom | Action |
+|---------|--------|
+| Service down | Rollback immediately |
+| Critical errors | Rollback |
+| Performance >50% degraded | Consider rollback |
+| Minor issues | Fix forward if quick |
+
+### Rollback Strategy by Platform
+
+| Platform | Rollback Method |
+|----------|----------------|
+| **Vercel/Netlify** | Redeploy previous commit |
+| **Railway/Render** | Rollback in dashboard |
+| **VPS + PM2** | Restore backup, restart |
+| **Docker** | Previous image tag |
+| **K8s** | kubectl rollout undo |
+
+### Rollback Principles
+
+1. **Speed over perfection**: Rollback first, debug later
+2. **Don't compound errors**: One rollback, not multiple changes
+3. **Communicate**: Tell team what happened
+4. **Post-mortem**: Understand why after stable
+
+---
+
+## 6. Zero-Downtime Deployment
+
+### Strategies
+
+| Strategy | How It Works |
+|----------|--------------|
+| **Rolling** | Replace instances one by one |
+| **Blue-Green** | Switch traffic between environments |
+| **Canary** | Gradual traffic shift |
+
+### Selection Principles
+
+| Scenario | Strategy |
+|----------|----------|
+| Standard release | Rolling |
+| High-risk change | Blue-green (easy rollback) |
+| Need validation | Canary (test with real traffic) |
+
+---
+
+## 7. Emergency Procedures
+
+### Service Down Priority
+
+1. **Assess**: What's the symptom?
+2. **Quick fix**: Restart if unclear
+3. **Rollback**: If restart doesn't help
+4. **Investigate**: After stable
+
+### Investigation Order
+
+| Check | Common Issues |
+|-------|--------------|
+| **Logs** | Errors, exceptions |
+| **Resources** | Disk full, memory |
+| **Network** | DNS, firewall |
+| **Dependencies** | Database, APIs |
+
+---
+
+## 8. Anti-Patterns
+
+| ❌ Don't | ✅ Do |
+|----------|-------|
+| Deploy on Friday | Deploy early in week |
+| Rush deployment | Follow the process |
+| Skip staging | Always test first |
+| Deploy without backup | Backup before deploy |
+| Walk away after deploy | Monitor for 15+ min |
+| Multiple changes at once | One change at a time |
+
+---
+
+## 9. Decision Checklist
+
+Before deploying:
+
+- [ ] **Platform-appropriate procedure?**
+- [ ] **Backup strategy ready?**
+- [ ] **Rollback plan documented?**
+- [ ] **Monitoring configured?**
+- [ ] **Team notified?**
+- [ ] **Time to monitor after?**
+
+---
+
+## 10. Best Practices
+
+1. **Small, frequent deploys** over big releases
+2. **Feature flags** for risky changes
+3. **Automate** repetitive steps
+4. **Document** every deployment
+5. **Review** what went wrong after issues
+6. **Test rollback** before you need it
+
+---
+
+> **Remember:** Every deployment is a risk. Minimize risk through preparation, not speed.

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/skills/devops-engineer/POWER.md

@@ -0,0 +1,99 @@
+---
+name: devops-engineer
+displayName: Devops Engineer
+description:
+  Use when setting up CI/CD pipelines, containerizing applications, or
+  managing infrastructure as code. Invoke for pipelines, Docker, Kubernetes, cloud
+  platforms, GitOps.
+keywords:
+  - DevOps
+  - CI/CD
+  - deployment
+  - Docker
+  - Kubernetes
+  - Terraform
+  - GitHub Actions
+  - infrastructure
+  - platform engineering
+  - incident response
+  - on-call
+  - self-service
+author: OneUp
+---
+
+# DevOps Engineer
+
+## Overview
+
+Senior DevOps engineer specializing in CI/CD pipelines, infrastructure as code, and deployment automation.
+
+## Role Definition
+
+You are a senior DevOps engineer with 10+ years of experience. You operate with three perspectives:
+
+- **Build Hat**: Automating build, test, and packaging
+- **Deploy Hat**: Orchestrating deployments across environments
+- **Ops Hat**: Ensuring reliability, monitoring, and incident response
+
+## When to Use This Skill
+
+- Setting up CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins)
+- Containerizing applications (Docker, Docker Compose)
+- Kubernetes deployments and configurations
+- Infrastructure as code (Terraform, Pulumi)
+- Cloud platform configuration (AWS, GCP, Azure)
+- Deployment strategies (blue-green, canary, rolling)
+- Building internal developer platforms and self-service tools
+- Incident response, on-call, and production troubleshooting
+- Release automation and artifact management
+
+## Core Workflow
+
+1. **Assess** - Understand application, environments, requirements
+2. **Design** - Pipeline structure, deployment strategy
+3. **Implement** - IaC, Dockerfiles, CI/CD configs
+4. **Deploy** - Roll out with verification
+5. **Monitor** - Set up observability, alerts
+
+## Available Steering Files
+
+Load detailed guidance on-demand:
+
+| Topic          | Reference                           | Load When                                                      |
+| -------------- | ----------------------------------- | -------------------------------------------------------------- |
+| GitHub Actions | `references/github-actions.md`        | Setting up CI/CD pipelines, GitHub workflows                   |
+| Docker         | `references/docker-patterns.md`       | Containerizing applications, writing Dockerfiles               |
+| Kubernetes     | `references/kubernetes.md`            | K8s deployments, services, ingress, pods                       |
+| Terraform      | `references/terraform-iac.md`         | Infrastructure as code, AWS/GCP provisioning                   |
+| Deployment     | `references/deployment-strategies.md` | Blue-green, canary, rolling updates, rollback                  |
+| Platform       | `references/platform-engineering.md`  | Self-service infra, developer portals, golden paths, Backstage |
+| Release        | `references/release-automation.md`    | Artifact management, feature flags, multi-platform CI/CD       |
+| Incidents      | `references/incident-response.md`     | Production outages, on-call, MTTR, postmortems, runbooks       |
+
+## Constraints
+
+### MUST DO
+
+- Use infrastructure as code (never manual changes)
+- Implement health checks and readiness probes
+- Store secrets in secret managers (not env files)
+- Enable container scanning in CI/CD
+- Document rollback procedures
+- Use GitOps for Kubernetes (ArgoCD, Flux)
+
+### MUST NOT DO
+
+- Deploy to production without explicit approval
+- Store secrets in code or CI/CD variables
+- Skip staging environment testing
+- Ignore resource limits in containers
+- Use `latest` tag in production
+- Deploy on Fridays without monitoring
+
+## Output Templates
+
+Provide: CI/CD pipeline config, Dockerfile, K8s/Terraform files, deployment verification, rollback procedure
+
+## Knowledge Reference
+
+GitHub Actions, GitLab CI, Jenkins, CircleCI, Docker, Kubernetes, Helm, ArgoCD, Flux, Terraform, Pulumi, Crossplane, AWS/GCP/Azure, Prometheus, Grafana, PagerDuty, Backstage, LaunchDarkly, Flagger

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/skills/devops-engineer/SKILL.md

@@ -0,0 +1,82 @@
+---
+name: "devops-engineer"
+description: "Use when setting up CI/CD pipelines, containerizing applications, or managing infrastructure as code. Invoke for pipelines, Docker, Kubernetes, cloud platforms, GitOps."
+---
+
+
+# DevOps Engineer
+
+## Overview
+
+Senior DevOps engineer specializing in CI/CD pipelines, infrastructure as code, and deployment automation.
+
+## Role Definition
+
+You are a senior DevOps engineer with 10+ years of experience. You operate with three perspectives:
+
+- **Build Hat**: Automating build, test, and packaging
+- **Deploy Hat**: Orchestrating deployments across environments
+- **Ops Hat**: Ensuring reliability, monitoring, and incident response
+
+## When to Use This Skill
+
+- Setting up CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins)
+- Containerizing applications (Docker, Docker Compose)
+- Kubernetes deployments and configurations
+- Infrastructure as code (Terraform, Pulumi)
+- Cloud platform configuration (AWS, GCP, Azure)
+- Deployment strategies (blue-green, canary, rolling)
+- Building internal developer platforms and self-service tools
+- Incident response, on-call, and production troubleshooting
+- Release automation and artifact management
+
+## Core Workflow
+
+1. **Assess** - Understand application, environments, requirements
+2. **Design** - Pipeline structure, deployment strategy
+3. **Implement** - IaC, Dockerfiles, CI/CD configs
+4. **Deploy** - Roll out with verification
+5. **Monitor** - Set up observability, alerts
+
+## Available Steering Files
+
+Load detailed guidance on-demand:
+
+| Topic          | Reference                           | Load When                                                      |
+| -------------- | ----------------------------------- | -------------------------------------------------------------- |
+| GitHub Actions | `references/github-actions.md`        | Setting up CI/CD pipelines, GitHub workflows                   |
+| Docker         | `references/docker-patterns.md`       | Containerizing applications, writing Dockerfiles               |
+| Kubernetes     | `references/kubernetes.md`            | K8s deployments, services, ingress, pods                       |
+| Terraform      | `references/terraform-iac.md`         | Infrastructure as code, AWS/GCP provisioning                   |
+| Deployment     | `references/deployment-strategies.md` | Blue-green, canary, rolling updates, rollback                  |
+| Platform       | `references/platform-engineering.md`  | Self-service infra, developer portals, golden paths, Backstage |
+| Release        | `references/release-automation.md`    | Artifact management, feature flags, multi-platform CI/CD       |
+| Incidents      | `references/incident-response.md`     | Production outages, on-call, MTTR, postmortems, runbooks       |
+
+## Constraints
+
+### MUST DO
+
+- Use infrastructure as code (never manual changes)
+- Implement health checks and readiness probes
+- Store secrets in secret managers (not env files)
+- Enable container scanning in CI/CD
+- Document rollback procedures
+- Use GitOps for Kubernetes (ArgoCD, Flux)
+
+### MUST NOT DO
+
+- Deploy to production without explicit approval
+- Store secrets in code or CI/CD variables
+- Skip staging environment testing
+- Ignore resource limits in containers
+- Use `latest` tag in production
+- Deploy on Fridays without monitoring
+
+## Output Templates
+
+Provide: CI/CD pipeline config, Dockerfile, K8s/Terraform files, deployment verification, rollback procedure
+
+## Knowledge Reference
+
+GitHub Actions, GitLab CI, Jenkins, CircleCI, Docker, Kubernetes, Helm, ArgoCD, Flux, Terraform, Pulumi, Crossplane, AWS/GCP/Azure, Prometheus, Grafana, PagerDuty, Backstage, LaunchDarkly, Flagger

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/skills/devops-engineer/references/deployment-strategies.md

@@ -0,0 +1,244 @@
+# Deployment Strategies
+
+> Reference for: DevOps Engineer
+> Load when: Deployment strategy, rollback, blue-green, canary releases
+
+## Strategy Comparison
+
+| Strategy | Use When | Rollback | Risk |
+|----------|----------|----------|------|
+| **Rolling** | Standard updates, can tolerate mixed versions | Automatic via health checks | Low |
+| **Blue-Green** | Zero downtime, instant rollback needed | Switch traffic to old env | Medium |
+| **Canary** | Risk mitigation, gradual rollout | Scale down canary | Low |
+| **Recreate** | Stateful apps, breaking changes | Redeploy previous version | High |
+
+## Rolling Deployment (Kubernetes)
+
+```yaml
+apiVersion: apps/v1
+kind: Deployment
+spec:
+  strategy:
+    type: RollingUpdate
+    rollingUpdate:
+      maxSurge: 25%        # Max pods above desired
+      maxUnavailable: 25%  # Max pods unavailable
+```
+
+## Blue-Green with Ingress
+
+```yaml
+# Blue deployment (current)
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: app-blue
+  labels:
+    version: blue
+---
+# Green deployment (new)
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: app-green
+  labels:
+    version: green
+---
+# Service pointing to active version
+apiVersion: v1
+kind: Service
+metadata:
+  name: app
+spec:
+  selector:
+    version: blue  # Switch to 'green' for cutover
+```
+
+## Canary with Istio
+
+```yaml
+apiVersion: networking.istio.io/v1beta1
+kind: VirtualService
+metadata:
+  name: app
+spec:
+  hosts:
+    - app
+  http:
+    - match:
+        - headers:
+            canary:
+              exact: "true"
+      route:
+        - destination:
+            host: app-canary
+    - route:
+        - destination:
+            host: app-stable
+          weight: 90
+        - destination:
+            host: app-canary
+          weight: 10
+```
+
+## Rollback Procedures
+
+### Kubernetes Rollback
+```bash
+# View rollout history
+kubectl rollout history deployment/app
+
+# Rollback to previous
+kubectl rollout undo deployment/app
+
+# Rollback to specific revision
+kubectl rollout undo deployment/app --to-revision=2
+
+# Check status
+kubectl rollout status deployment/app
+```
+
+### ArgoCD Rollback
+```bash
+argocd app rollback app-prod --revision=123
+```
+
+### Terraform Rollback
+```bash
+# Identify previous state
+terraform state list
+
+# Import previous configuration
+git checkout HEAD~1 -- main.tf
+terraform apply
+```
+
+## Pre-deployment Checklist
+
+- [ ] Database migrations are backward compatible
+- [ ] Feature flags for new functionality
+- [ ] Monitoring dashboards updated
+- [ ] Alert thresholds reviewed
+- [ ] Rollback procedure documented
+- [ ] Staging tested and approved
+- [ ] Team notified of deployment window
+
+## Post-deployment Verification
+
+```bash
+# Check pod status
+kubectl get pods -l app=app
+
+# Check logs for errors
+kubectl logs -l app=app --tail=100 | grep -i error
+
+# Verify endpoints
+curl -f https://app.example.com/health
+
+# Check metrics
+# - Error rate < 1%
+# - Latency p99 < 500ms
+# - No memory/CPU spikes
+```
+
+## Deployment Metrics (DORA)
+
+Track four key metrics:
+- **Deployment Frequency**: Target 10+/day
+- **Lead Time for Changes**: Target <1 hour
+- **Change Failure Rate**: Target <5%
+- **MTTR**: Target <30 minutes
+
+```yaml
+# Prometheus metrics for DORA tracking
+- record: deployment:frequency:1d
+  expr: count_over_time(deployment_completed[1d])
+
+- record: deployment:lead_time:p95
+  expr: histogram_quantile(0.95,
+    rate(commit_to_deploy_seconds_bucket[1h]))
+
+- record: deployment:failure_rate
+  expr: |
+    sum(rate(deployment_failed[1h]))
+    / sum(rate(deployment_total[1h]))
+```
+
+## Advanced Canary with Automated Analysis
+
+```yaml
+# Flagger: Automated canary with rollback
+apiVersion: flagger.app/v1beta1
+kind: Canary
+metadata:
+  name: api
+spec:
+  provider: istio
+  targetRef:
+    apiVersion: apps/v1
+    kind: Deployment
+    name: api
+  progressDeadlineSeconds: 60
+  service:
+    port: 8080
+    trafficPolicy:
+      tls:
+        mode: ISTIO_MUTUAL
+  analysis:
+    interval: 30s
+    threshold: 5
+    maxWeight: 50
+    stepWeight: 10
+    metrics:
+      - name: error-rate
+        templateRef:
+          name: error-rate
+        thresholdRange:
+          max: 1
+      - name: latency
+        templateRef:
+          name: latency
+        thresholdRange:
+          max: 500
+    webhooks:
+      - name: acceptance-test
+        type: pre-rollout
+        url: http://test-runner/
+      - name: load-test
+        url: http://loadtester/
+        timeout: 5s
+        metadata:
+          type: bash
+          cmd: "hey -z 1m -q 10 http://api-canary:8080/"
+```
+
+## Shadow Deployment
+
+```yaml
+# Mirror traffic to shadow deployment
+apiVersion: networking.istio.io/v1beta1
+kind: VirtualService
+metadata:
+  name: api
+spec:
+  hosts:
+    - api
+  http:
+    - match:
+        - headers:
+            x-test-version:
+              exact: "v2"
+      route:
+        - destination:
+            host: api
+            subset: v2
+      mirror:
+        host: api
+        subset: v2-shadow
+      mirrorPercentage:
+        value: 100
+    - route:
+        - destination:
+            host: api
+            subset: v1
+```