kubernetes principles
- Repo stars 0
- Author repo skills-registry
- Domain
- DevOps
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Kubernetes Principles
Use this skill as standing guidance for this domain. Apply the checklist first; read the detailed reference only when the task is substantial, risky, unfamiliar, or review-oriented.
## Operating Rules
- Prefer the repository's existing conventions, toolchain, and CI commands over generic defaults.
- Make the smallest coherent change that satisfies the request while preserving behavior.
- Treat tests, linting, dependency hygiene, and security review as part of completion.
- If a principle conflicts with higher-priority repository instructions or an explicit user request, follow the higher-priority instruction and call out the tradeoff.
## Core Checklist
- Set requests, limits, probes, disruption budgets, and rollout strategy deliberately for production workloads.
- Use namespace boundaries, least-privilege RBAC, and network policies for isolation.
- Follow Kubernetes Pod Security Standards; default application workloads toward the Restricted profile.
- Run containers as non-root, drop unnecessary capabilities, and avoid host namespaces and privileged containers.
- Store configuration in ConfigMaps and secrets appropriately; do not commit plaintext secrets.
- Validate Helm templates, CRDs, and manifests against schemas and policy before applying.
- Use labels and annotations consistently for ownership, observability, selection, and lifecycle automation.
- Design upgrades and rollbacks before changing stateful workloads, ingress, storage, or networking.
## Validation
Run applicable checks when they exist in the project; if a tool is missing, report that it was skipped.
- `helm lint` for charts
- `helm template ... | kubeconform -strict` or schema validation for rendered manifests
- Policy checks with Kyverno, Gatekeeper/OPA, Conftest, or the project's admission policy tooling
## Detailed Reference
For the complete principle set with examples and edge cases, read [references/principles.md](references/principles.md) when deeper guidance is useful.
---
> Source: [asciifylabs/asciify-skills](https://github.com/asciifylabs/asciify-skills) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
Sections and files
Listed in source order.
sections -> Operating Rules → Core Checklist → Validation → Detailed Reference
terms -> Use this skill as standing guidance for this domain. · - Prefer the repository's existing conventions, toolchain, and CI commands over generic defaults. · - Set requests, limits, probes, disruption budgets, and rollout strategy deliberately for production workloads. · Run applicable checks when they exist in the project; if a tool is missing, report that it was skipped. · - helm lint for charts - helm template ... · --- > Source: [asciifylabs/asciify-skills](https://github.com/asciifylabs/asciify-skills) — distributed by [TomeVault](https://tomevault.io).
files/cmd -> helm lint · helm template ... | kubeconform -strict · Gatekeeper/OPA · references/principles.md · asciifylabs/asciify-skills · github.com/asciifylabs/asciify-skills
body sha256 -> 9c28bd1cca26
Operating Rules
Prefer the repository's existing conventions, toolchain, and CI commands over generic defaults. Make the smallest coherent change that satisfies the request while preserving behavior. Treat tests, linting, dependency hygiene, and security review as part of completion. If a principle conflicts with higher-priority repository instructions or an explicit user request, follow the higher-priority instruction and call out the tradeoff.
Core Checklist
Set requests, limits, probes, disruption budgets, and rollout strategy deliberately for production workloads. Use namespace boundaries, least-privilege RBAC, and network policies for isolation. Follow Kubernetes Pod Security Standards; default application workloads toward the Restricted profile. Run containers as non-root, drop unnecessary capabilities, and avoid host namespaces and privileged containers.
Validation
Run applicable checks when they exist in the project; if a tool is missing, report that it was skipped.
helm lintfor chartshelm template ... | kubeconform -strictor schema validation for rendered manifests Policy checks with Kyverno, Gatekeeper/OPA, Conftest, or the project's admission policy toolingDetailed Reference
For the complete principle set with examples and edge cases, read references/principles.md when deeper guidance is useful. Source: asciifylabs/asciify-skills — distributed by TomeVault.