What problem does it solve? Writing Helm charts that render correctly, upgrade safely, and follow community conventions is error-prone: version bumps get skipped, numeric labels break upgrades, ConfigMap changes never restart pods, and secrets leak into values files. This Skill encodes Helm chart best practices so charts are structured, validated, and upgrade-safe from the start. ## Core Features & Use Cases - Chart structure and versioning: Correct Chart.yaml anatomy, chart SemVer vs appVersion discipline, .helmignore, labels, hooks, and CRD lifecycle rules. - Values design and validation: values.yaml conventions, the image.tag to appVersion fallback pattern, values.schema.json validation, and safe secret handling via existingSecret and secretKeyRef. - Templating and upgrade safety: _helpers.tpl and include patterns, whitespace control, the numeric-label quoting trap, helm lint/template/unittest workflows, --wait/--atomic semantics, and checksum annotations that roll pods on config changes. - Use Case: When packaging a Kubernetes application as a chart, use this Skill to scaffold the chart, design values.yaml, add a values.schema.json, and set up CI rendering checks before the first helm install. ## Quick Start Ask the AI to create a Helm chart for your application with a values.schema.json, standard app.kubernetes.io labels, and a config checksum annotation on the Deployment.