What problem does it solve? Helm chart values often ship without documentation or schema validation, leaving users guessing what each key does and IDEs unable to validate edits. This Skill enforces a consistent annotation convention so every values.yaml entry carries a helm-docs description and helm-schema type constraints. ## Core Features & Use Cases - Annotation conventions: Defines the exact comment order (# @schema block, then # -- description, then the key) so helm-docs and helm-schema parse values.yaml correctly. - Values structure guidance: Prescribes a standard grouping order for values (replicas, image, service account, security, networking, resources, autoscaling, scheduling, escape hatches, sub-charts). - Automation setup: Covers generating README.md with helm-docs, generating values.schema.json with helm-schema, wiring both as pre-commit hooks, and enabling IDE validation via the yaml-language-server schema line. - Use Case: When adding a new autoscaling section to a chart's values.yaml, apply the correct enum, minimum, and description annotations, then regenerate values.schema.json and the README values table so both stay in sync. ## Quick Start Ask the assistant to add a new annotated value to values.yaml following the helm-docs and helm-schema conventions, then regenerate the schema and README documentation.
