Design cluster networking: Gateway API ingress for north-south, and a service mesh ONLY when it earns its complexity (mTLS-everywhere, traffic-splitting, per-call resilience). Wire mTLS, weighted canary routing, and resilience deliberately.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cloud-native-kubernetes:ingress-and-meshThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Gateway API for north-south + TLS. The cloud LB sits behind it (cloud plugin).
Gateway API for north-south + TLS. The cloud LB sits behind it (cloud plugin).
Add a mesh for mTLS-everywhere, traffic-splitting (canary), or per-call resilience across many services. It costs latency + memory + ops. Name the capability you're buying.
npx claudepluginhub mcorbett51090/ravenclaude --plugin cloud-native-kubernetesGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.