What problem does it solve? Helm chart development is full of subtle pitfalls — Go template falsy-value traps, subchart value merging quirks, and documentation drift between values.yaml and README files. This Skill encodes production-grade conventions for writing, documenting, and testing Helm charts so these mistakes are caught before they ship. ## Core Features & Use Cases - Helm template best practices: Conventions for named helpers in _*.tpl files, whitespace trimming, context passing, and avoiding the default function's falsy-value trap by using dig or hasKey. - helm-docs annotation conventions: Rules for # --, @notationType, @default, and @raw comments so chart READMEs and values references generate correctly from values.yaml. - Subchart wrapping guidance: How deep-merging works, when to use null to clear upstream defaults, and how subchart validation templates can fail your render. - Testing with helm-unittest: Test layout, path resolution gotchas, deterministic snapshot stubs, and BDD-style assertions. - Use Case: When adding a new boolean flag to a chart's values.yaml, the Skill ensures you write the template condition correctly, annotate the value for helm-docs, and add unit tests covering both the true and false cases. ## Quick Start Use the chart-development skill to add a new configurable value to the Helm chart with proper helm-docs annotations and a helm-unittest test.
