npx claudepluginhub levifig/loaf --plugin loafWant just this skill?
Then install: npx claudepluginhub u/[userId]/[slug]
Covers Docker, Kubernetes, GitOps, CI/CD pipelines, and container security.
This skill is limited to using the following tools:
references/ci-cd.mdreferences/docker.mdreferences/gitops.mdreferences/kubernetes.mdreferences/troubleshooting.mdscripts/check-dockerfile.shscripts/validate-k8s-manifest.pyInfrastructure
Infrastructure patterns for containerization, orchestration, CI/CD pipelines, and deployment automation.
Stack Overview
| Layer | Technologies |
|---|---|
| Containers | Docker, BuildKit, multi-stage builds |
| Orchestration | Kubernetes, Helm, Kustomize |
| GitOps | ArgoCD, Flux, Argo Rollouts |
| CI/CD | GitHub Actions, GitLab CI |
| Registries | GHCR, ECR, GCR, DockerHub |
Topics
| Topic | Reference File | Use When |
|---|---|---|
| Docker | references/docker.md | Writing Dockerfiles, optimizing builds, adding health checks |
| Kubernetes | references/kubernetes.md | Creating deployments, services, probes, resource limits |
| GitOps | references/gitops.md | Setting up ArgoCD, Kustomize, sync policies |
| CI/CD | references/ci-cd.md | Building GitHub Actions workflows, caching, secrets |
| Troubleshooting | references/troubleshooting.md | Debugging CI failures, version conflicts, cache issues |
Available Scripts
| Script | Usage | Description |
|---|---|---|
scripts/check-dockerfile.sh | check-dockerfile.sh <file> | Validate Dockerfile best practices |
scripts/validate-k8s-manifest.py | validate-k8s-manifest.py <file> | Check K8s manifest for required fields |
Critical Rules
Always
- Use multi-stage builds to minimize image size
- Run containers as non-root user (UID 1000)
- Include health checks in all services
- Pin specific image versions (no
:latest) - Set resource requests AND limits
- Use
npm ci/pip-syncin CI (not install) - Commit lockfiles to version control
Never
- Commit secrets to version control
- Use
:latesttags in production - Skip security scanning in CI
- Deploy without rollback capability
- Store state in containers
- Run as root in production
CI Failure Triage
CI Failed
+-- Same code passes locally?
| +-- YES --> Check environment differences
| | +-- Python/Node version
| | +-- Environment variables
| | +-- File permissions
| | +-- Installed dependencies
| +-- NO --> Fix the actual bug
+-- Flaky (sometimes passes)?
| +-- Check for race conditions, shared state, timeouts
+-- Always fails in CI?
+-- Check runner resources (memory, timeout)
+-- Check external service access
+-- Check CI-specific config
Similar Skills
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
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.