菜单
Design CRD schemas, webhooks, reconcile loops, status models, and RBAC for Kubernetes operators. Use when Codex needs to define or review the API shape and control-plane behavior of a Kubebuilder-style operator.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Debug failing Go tests, panics, race reports, and flaky behavior with Delve and a breakpoint-first hypothesis loop. Use when Codex needs runtime evidence instead of more static reasoning, especially after a targeted Go test failure.
Follow an opinionated Go feedback loop with targeted tests, linting, local CI, security scans, dependency audits, coverage, benchmarking, generation, and migrations. Use when Codex is modifying Go code, setting up repeatable repo scripts, or tightening validation after a Go change.
Review Kubernetes operators for safety, CRD quality, webhook correctness, RBAC scope, controller behavior, and local dev-loop readiness. Use when Codex is auditing an operator implementation or deciding whether a change is ready for testing or release.
Provide starter files for a Kubernetes operator dev loop, including Tilt, Kustomize dev overlays, Make targets, and a minimal Dockerfile. Use when Codex needs to create or refresh local scaffolding around a Kubebuilder-style operator.
Guide Kubernetes operator development with Kubebuilder, kind, Tilt, and Kustomize. Use when Codex needs to scaffold or iterate on CRDs, controllers, or webhooks; stand up a safe local kind cluster; run a fast operator dev loop; or verify CRDs, pods, and webhook state.
Create polished programmatic product demo videos from software projects using a bundled Remotion template, storyboard generation, and TTS narration. Use when Codex needs to turn an app, library, CLI, or API into a demo video without screen recording, or when iterating on storyboard scenes, narration, or renders.
| name | k8s-crd-design |
| description | Design CRD schemas, webhooks, reconcile loops, status models, and RBAC for Kubernetes operators. Use when Codex needs to define or review the API shape and control-plane behavior of a Kubebuilder-style operator. |
Use these patterns when designing and implementing CRDs, webhooks, controllers, and RBAC for Kubernetes operators.
Before writing code:
Propose:
spec fields with types, validation markers, and requirednessstatus fields for observed state, conditions, and generation trackingkubectl get outputEnable the status subresource when the CR reports status.
Ignore in local dev if availability matters more than strict enforcement.Fail when the environment requires safety over availability.Follow this sequence:
Keep the reconcile function idempotent and level-triggered.
Grant only the verbs and resources the controller needs:
get, list, watch, patch, update on status if usedcreate and patchAvoid wildcards and cluster-wide scope unless the resource model requires it.
Minimum coverage: