Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.
Creates CI/CD pipelines, containerizes applications, and deploys to Kubernetes using infrastructure as code patterns.
/plugin marketplace add yonatangross/orchestkit/plugin install orkl@orchestkitThis skill inherits all available tools. When active, it can use any tool Claude has access to.
checklists/production-readiness.mdexamples/github-actions-cicd.mdreferences/ci-cd-pipelines.mdreferences/deployment-strategies.mdreferences/docker-patterns.mdreferences/environment-management.mdreferences/kubernetes-basics.mdreferences/multi-service-setup.mdreferences/nixpacks-customization.mdreferences/observability.mdreferences/railway-json-config.mdrules/_sections.mdrules/_template.mdrules/devops-branch-protection.mdrules/devops-ci-caching.mdrules/devops-db-migrations.mdrules/docker-layer-security.mdrules/docker-multistage.mdrules/railway-deployment.mdscripts/DockerfileComprehensive frameworks for CI/CD pipelines, containerization, deployment strategies, and infrastructure automation.
┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Code │──>│ Build │──>│ Test │──>│ Deploy │
│ Commit │ │ & Lint │ │ & Scan │ │ & Release │
└─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘
│ │ │ │
v v v v
Triggers Artifacts Reports Monitoring
Multi-stage builds minimize image size:
Security hardening:
Essential manifests:
Security context:
runAsNonRoot: trueallowPrivilegeEscalation: falsereadOnlyRootFilesystem: true| Strategy | Use Case | Risk |
|---|---|---|
| Rolling | Default, gradual replacement | Low - automatic rollback |
| Blue-Green | Instant switch, easy rollback | Medium - double resources |
| Canary | Progressive traffic shift | Low - gradual exposure |
Rolling Update (Kubernetes default):
strategy:
type: RollingUpdate
rollingUpdate:
maxSurge: 25%
maxUnavailable: 0 # Zero downtime
Use External Secrets Operator to sync from cloud providers:
See: references/docker-patterns.md
Key topics covered:
See: references/ci-cd-pipelines.md
Key topics covered:
See: references/kubernetes-basics.md
Key topics covered:
See: references/environment-management.md
Key topics covered:
See: references/observability.md
Key topics covered:
See: rules/railway-deployment.md
Key topics covered:
references/railway-json-config.md, references/nixpacks-customization.md, references/multi-service-setup.mdSee: references/deployment-strategies.md
Key topics covered:
charts/app/
├── Chart.yaml
├── values.yaml
├── scripts/
│ ├── deployment.yaml
│ ├── service.yaml
│ ├── ingress.yaml
│ ├── configmap.yaml
│ ├── secret.yaml
│ ├── hpa.yaml
│ └── _helpers.tpl
└── values/
├── staging.yaml
└── production.yaml
zero-downtime-migration - Database migration patterns for zero-downtime deploymentssecurity-scanning - Security scanning integration for CI/CD pipelinesork:monitoring-observability - Monitoring and alerting for deployed applicationsork:database-patterns - Python/Alembic migration workflow for backend deployments| Decision | Choice | Rationale |
|---|---|---|
| Container user | Non-root (uid 1001) | Security best practice, required by many orchestrators |
| Deployment strategy | Rolling update (default) | Zero downtime, automatic rollback, resource efficient |
| Secrets management | External Secrets Operator | Syncs from cloud providers, GitOps compatible |
| Health checks | Separate startup/liveness/readiness | Prevents premature traffic, enables graceful shutdown |
Use Opus 4.6 adaptive thinking for:
| Template | Purpose |
|---|---|
github-actions-pipeline.yml | Full CI/CD workflow with 6 stages |
Dockerfile | Multi-stage Node.js build |
docker-compose.yml | Development environment |
k8s-manifests.yaml | Deployment, Service, Ingress |
helm-values.yaml | Helm chart values |
terraform-aws.tf | VPC, EKS, RDS infrastructure |
argocd-application.yaml | GitOps application |
external-secrets.yaml | Secrets Manager integration |
Keywords: ci, cd, pipeline, github actions, gitlab ci, jenkins, workflow Solves:
Keywords: docker, dockerfile, container, image, build, compose, multi-stage Solves:
Keywords: kubernetes, k8s, deployment, service, ingress, helm, statefulset, pdb Solves:
Keywords: terraform, pulumi, iac, infrastructure, provision, gitops, argocd Solves:
Keywords: blue green, canary, rolling, deployment strategy, rollback, zero downtime Solves:
Keywords: prometheus, grafana, metrics, alerting, monitoring, health check Solves:
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.