What problem does it solve? Platform teams building an Internal Developer Platform on Kubernetes need consistent rules for shipping baseline cluster addons and reusable application building blocks. Without encoded conventions, Helm charts drift in naming, testing, dependency management, and GitOps structure, causing render-time failures and unreviewable PRs. ## Core Features & Use Cases - Layered blueprint architecture: Enforces a five-layer model (AKS Terraform foundation → ArgoCD App-of-Apps baseline addons → commons library charts → building-block charts → product charts) with one-way downward dependencies. - Nine non-negotiable rules: OCI-only chart dependencies, | trunc 63 | trimSuffix "-" on every name template, quoted Crossplane forProvider strings, camelCase Helm values vs snake_case ArgoCD values, and wrapper-chart helm-unittest testing. - Four-tier validation gate: Standardizes yamllint → helm lint → helm-unittest → kubeconform locally and in CI, with Helm pinned to v3.20.0. - Use Case: When asked to "add a new addon" like cert-manager to a GitOps repo, the skill walks through creating addon_charts/<name>/, wiring the base_chart/templates/{NN}-<name>.yaml Application with the correct sync wave, and updating values.yaml. ## Quick Start Ask the AI to add a new addon such as cert-manager to the baseline GitOps repository following the platform's sync-wave and values conventions.