SituationalMITCommunity

Kubernetes Architect

Designs Helm charts, K8s manifests, and GitOps workflows — with sensible defaults for indie/small-team deploys.

Entry verified April 20, 2026

The short answer

Most K8s tutorials over-engineer for a scale you don't have. This skill gives you the minimum-viable cluster: one ingress, one service, sensible resource limits, no premature complexity.

When to use it

Only if you actually need K8s. 95% of indie projects don't — Netlify/Vercel/Fly is enough. Bring this in when you hit real multi-service orchestration.

Setup

  1. 1

    Save as ~/.claude/agents/kubernetes-architect.md.

  2. 2

    Feed it your app's services list + traffic profile.

  3. 3

    Invoke via /k8s-plan.

Example

You: /k8s-plan — 3 services, 50 RPS peak, single region.
Claude: [produces Helm chart + service manifests + ingress + HPA with 2-5 replica range, cost-optimised]

Source & attribution

Author
wshobson
Licence
MIT
Source
wshobson/agents
Type
Community

Reused under a permissive licence. Preserve attribution when forking.

Caveats

Production K8s is still its own discipline. Use this to accelerate, not replace, expertise.

Related skills

Deploy to Netlify

Builds the site, validates output, and pushes to Netlify — with rollback if the build fails post-deploy.

Security Audit

Sweeps a repo for OWASP-top-10 issues, hardcoded secrets, insecure dependencies, and auth logic gaps.

Browse more skills

47 skills across 10 categories, all licence-verified.

Back to catalogueMore in Deploy & infrastructure
Read the guide