[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EN7TTS840Z7B40BMS9SH89":3,"skill-same:01M7EN7TTS840Z7B40BMS9SH89":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EN7TTS840Z7B40BMS9SH89","helm-pro",null,"Helm guidance — chart structure, templating, values management, releases, hooks, and chart best practices.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-helm-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: helm-pro\ndescription: Helm guidance — chart structure, templating, values management, releases, hooks, and chart best practices.\ncategory: development\n---\n\n## Overview\n\nHelm is the package manager for Kubernetes: charts bundle manifests with templating, values files customize per environment, and releases track what's deployed with rollback support. For third-party software (databases, ingress controllers, monitoring), Helm charts are the standard distribution format; for your own apps, charts are one packaging option among several.\n\nHelm's templating is powerful and easy to abuse — charts drift into unmaintainable Go-template spaghetti without discipline. This skill covers chart structure, values management across environments, safe release practices, and when to prefer Kustomize or plain manifests instead.\n\n## When to use\n\n- Packaging an application as a Helm chart.\n- Managing environment differences with values files.\n- Deploying third-party charts (choosing versions, values).\n- Debugging templating errors and failed releases.\n- Using Helm hooks, tests, and OCI registries.\n- Choosing between Helm, Kustomize, and plain manifests.\n- Operating Helm releases in production (rollbacks, upgrades).\n\n## Core concepts\n\n- **Charts.** A chart is a directory: `Chart.yaml` (metadata), `values.yaml` (defaults), `templates\u002F` (manifests), optional `charts\u002F` (subcharts). Charts version independently of the app (`version` vs `appVersion`).\n- **Values.** `values.yaml` defaults overridden by `-f` files and `--set` flags — later sources win. Per-environment values files (`values-prod.yaml`) are the standard environment mechanism. `--set` for one-offs, files for anything persistent.\n- **Templating.** Go templates with Helm's functions (`{{ .Values.replicaCount }}`, `{{ include \"chart.name\" . }}`). Keep templates readable: named templates (`_helpers.tpl`) for repeated snippets, minimal logic in templates, validation via `required` and `fail`.\n- **Release management.** `helm install\u002Fupgrade --install` with `--atomic` (rollback on failure) and `--wait`; release history enables `helm rollback`. Releases are namespaced; names should be stable per environment.\n- **Hooks.** `pre-install`, `post-upgrade`, `pre-delete` etc. for jobs that run outside the normal lifecycle (DB migrations, backups). Hooks have their own deletion policies — misconfigured hooks linger or never run.\n- **Tests.** `helm test` runs test pods defined in `templates\u002Ftests\u002F` — smoke tests executed post-install. Cheap verification that the release actually works.\n- **Dependencies.** `Chart.yaml` dependencies on other charts (databases, etc.) with version constraints; `helm dependency update` vendors them. Pin versions — floating dependencies break installs.\n- **OCI registries.** Charts stored as OCI artifacts (`helm push oci:\u002F\u002F...`) — chart distribution through the same registry as images, with the same auth and immutability semantics.\n- **Lint and template.** `helm lint` catches chart errors; `helm template` renders locally for inspection and diffing. Run both in CI before any install.\n- **Values schema.** `values.schema.json` validates values files — catches typos and type errors before they become failed releases. Write schemas for charts others consume.\n- **Secrets.** Values files are plaintext — don't put secrets in them. Reference external secret stores, use `--set` from CI secrets sparingly, or template from mounted secrets.\n- **Chart sources.** Artifact Hub for discovery; prefer official\u002Fverified charts; pin chart versions in dependencies and deployments — `latest` charts are undebuggable.\n- **Helm vs Kustomize.** Helm: parameterization and packaging (great for distributing software). Kustomize: overlays without templates (great for your own apps' environment diffs). Many teams use Helm for third-party + Kustomize for first-party.\n- **Release naming.** Consistent naming (`\u003Capp>-\u003Cenv>`) so releases are greppable; avoid generating names with timestamps — releases should be stable identities.\n- **Dry run and diff.** `helm upgrade --dry-run` and the diff plugin show what will change before it changes — the plan\u002Fapply equivalent. Review diffs like code.\n\n## Practical workflow\n\n1. **Structure the chart.** Standard layout; `values.yaml` with documented defaults; `_helpers.tpl` for naming\u002Flabels; one template file per resource kind.\n   ```\n   shop-api\u002F\n     Chart.yaml  values.yaml  values-prod.yaml\n     values.schema.json\n     templates\u002F{deployment,service,ingress,hpa,tests}\u002F  _helpers.tpl\n   ```\n2. **Write clean templates.** Named helpers for labels\u002Fselectors; `required` for mandatory values with clear error messages; keep conditionals shallow.\n   ```yaml\n   # templates\u002Fdeployment.yaml (excerpt)\n   replicas: {{ .Values.replicaCount }}\n   image: \"{{ .Values.image.repository }}:{{ .Values.image.tag | default .Chart.AppVersion }}\"\n   ```\n3. **Manage values per environment.** Base `values.yaml` + `values-prod.yaml` overrides; schema validation; secrets from external stores, never in values files.\n4. **Lint, template, diff in CI.** `helm lint`, `helm template` rendering checks, diff against the live release — the review gate before upgrade.\n5. **Deploy safely.** `helm upgrade --install --atomic --wait --timeout 10m -f values-prod.yaml`; hooks for migrations with proper delete policies; `helm test` smoke tests after.\n   ```bash\n   helm upgrade --install shop-api .\u002Fshop-api \\\n     -f values.yaml -f values-prod.yaml \\\n     --namespace shop-prod --atomic --wait --timeout 10m\n   ```\n6. **Handle third-party charts.** Pin chart versions; values files for your overrides (never edit the chart); track upstream changes before upgrading.\n7. **Use hooks deliberately.** Migration jobs as pre-upgrade hooks with `before-hook-creation` delete policy; verify hook completion in the release pipeline.\n8. **Publish and version.** OCI registry for chart storage; semantic versioning for chart changes; changelog per release; deprecate values keys with warnings before removing.\n\n## Common pitfalls\n\n- **Template spaghetti** — deeply nested conditionals and string building; keep logic minimal, validate inputs.\n- **Secrets in values files** — plaintext credentials in git; external secret management.\n- **Unpinned chart versions** — floating dependencies breaking installs; pin everything.\n- **No values schema** — typos becoming failed releases; `values.schema.json` for shared charts.\n- **Skipping diff review** — upgrading blind; diff before every upgrade.\n- **Non-atomic upgrades** — half-applied releases on failure; `--atomic` for rollback.\n- **Hook misconfiguration** — hooks that never run or never clean up; set hook weights and delete policies.\n- **Editing third-party charts** — forked charts drifting from upstream; override via values, contribute fixes upstream.\n- **`--set` for complex config** — escaping hell; values files for anything non-trivial.\n- **Release name instability** — generated names breaking tooling; stable names per environment.\n- **Ignoring `helm test`** — no post-install verification; add smoke tests.\n- **Chart version vs appVersion confusion** — bumping the wrong one; chart version for chart changes, appVersion for the app.\n- **Storing charts in git without registry** — no immutability story; OCI registries for distribution.\n","## Overview\n\nHelm is the package manager for Kubernetes: charts bundle manifests with templating, values files customize per environment, and releases track what's deployed with rollback support. For third-party software (databases, ingress controllers, monitoring), Helm charts are the standard distribution format; for your own apps, charts are one packaging option among several.\n\nHelm's templating is powerful and easy to abuse — charts drift into unmaintainable Go-template spaghetti without discipline. This skill covers chart structure, values management across environments, safe release practices, and when to prefer Kustomize or plain manifests instead.\n\n## When to use\n\n- Packaging an application as a Helm chart.\n- Managing environment differences with values files.\n- Deploying third-party charts (choosing versions, values).\n- Debugging templating errors and failed releases.\n- Using Helm hooks, tests, and OCI registries.\n- Choosing between Helm, Kustomize, and plain manifests.\n- Operating Helm releases in production (rollbacks, upgrades).\n\n## Core concepts\n\n- **Charts.** A chart is a directory: `Chart.yaml` (metadata), `values.yaml` (defaults), `templates\u002F` (manifests), optional `charts\u002F` (subcharts). Charts version independently of the app (`version` vs `appVersion`).\n- **Values.** `values.yaml` defaults overridden by `-f` files and `--set` flags — later sources win. Per-environment values files (`values-prod.yaml`) are the standard environment mechanism. `--set` for one-offs, files for anything persistent.\n- **Templating.** Go templates with Helm's functions (`{{ .Values.replicaCount }}`, `{{ include \"chart.name\" . }}`). Keep templates readable: named templates (`_helpers.tpl`) for repeated snippets, minimal logic in templates, validation via `required` and `fail`.\n- **Release management.** `helm install\u002Fupgrade --install` with `--atomic` (rollback on failure) and `--wait`; release history enables `helm rollback`. Releases are namespaced; names should be stable per environment.\n- **Hooks.** `pre-install`, `post-upgrade`, `pre-delete` etc. for jobs that run outside the normal lifecycle (DB migrations, backups). Hooks have their own deletion policies — misconfigured hooks linger or never run.\n- **Tests.** `helm test` runs test pods defined in `templates\u002Ftests\u002F` — smoke tests executed post-install. Cheap verification that the release actually works.\n- **Dependencies.** `Chart.yaml` dependencies on other charts (databases, etc.) with version constraints; `helm dependency update` vendors them. Pin versions — floating dependencies break installs.\n- **OCI registries.** Charts stored as OCI artifacts (`helm push oci:\u002F\u002F...`) — chart distribution through the same registry as images, with the same auth and immutability semantics.\n- **Lint and template.** `helm lint` catches chart errors; `helm template` renders locally for inspection and diffing. Run both in CI before any install.\n- **Values schema.** `values.schema.json` validates values files — catches typos and type errors before they become failed releases. Write schemas for charts others consume.\n- **Secrets.** Values files are plaintext — don't put secrets in them. Reference external secret stores, use `--set` from CI secrets sparingly, or template from mounted secrets.\n- **Chart sources.** Artifact Hub for discovery; prefer official\u002Fverified charts; pin chart versions in dependencies and deployments — `latest` charts are undebuggable.\n- **Helm vs Kustomize.** Helm: parameterization and packaging (great for distributing software). Kustomize: overlays without templates (great for your own apps' environment diffs). Many teams use Helm for third-party + Kustomize for first-party.\n- **Release naming.** Consistent naming (`\u003Capp>-\u003Cenv>`) so releases are greppable; avoid generating names with timestamps — releases should be stable identities.\n- **Dry run and diff.** `helm upgrade --dry-run` and the diff plugin show what will change before it changes — the plan\u002Fapply equivalent. Review diffs like code.\n\n## Practical workflow\n\n1. **Structure the chart.** Standard layout; `values.yaml` with documented defaults; `_helpers.tpl` for naming\u002Flabels; one template file per resource kind.\n   ```\n   shop-api\u002F\n     Chart.yaml  values.yaml  values-prod.yaml\n     values.schema.json\n     templates\u002F{deployment,service,ingress,hpa,tests}\u002F  _helpers.tpl\n   ```\n2. **Write clean templates.** Named helpers for labels\u002Fselectors; `required` for mandatory values with clear error messages; keep conditionals shallow.\n   ```yaml\n   # templates\u002Fdeployment.yaml (excerpt)\n   replicas: {{ .Values.replicaCount }}\n   image: \"{{ .Values.image.repository }}:{{ .Values.image.tag | default .Chart.AppVersion }}\"\n   ```\n3. **Manage values per environment.** Base `values.yaml` + `values-prod.yaml` overrides; schema validation; secrets from external stores, never in values files.\n4. **Lint, template, diff in CI.** `helm lint`, `helm template` rendering checks, diff against the live release — the review gate before upgrade.\n5. **Deploy safely.** `helm upgrade --install --atomic --wait --timeout 10m -f values-prod.yaml`; hooks for migrations with proper delete policies; `helm test` smoke tests after.\n   ```bash\n   helm upgrade --install shop-api .\u002Fshop-api \\\n     -f values.yaml -f values-prod.yaml \\\n     --namespace shop-prod --atomic --wait --timeout 10m\n   ```\n6. **Handle third-party charts.** Pin chart versions; values files for your overrides (never edit the chart); track upstream changes before upgrading.\n7. **Use hooks deliberately.** Migration jobs as pre-upgrade hooks with `before-hook-creation` delete policy; verify hook completion in the release pipeline.\n8. **Publish and version.** OCI registry for chart storage; semantic versioning for chart changes; changelog per release; deprecate values keys with warnings before removing.\n\n## Common pitfalls\n\n- **Template spaghetti** — deeply nested conditionals and string building; keep logic minimal, validate inputs.\n- **Secrets in values files** — plaintext credentials in git; external secret management.\n- **Unpinned chart versions** — floating dependencies breaking installs; pin everything.\n- **No values schema** — typos becoming failed releases; `values.schema.json` for shared charts.\n- **Skipping diff review** — upgrading blind; diff before every upgrade.\n- **Non-atomic upgrades** — half-applied releases on failure; `--atomic` for rollback.\n- **Hook misconfiguration** — hooks that never run or never clean up; set hook weights and delete policies.\n- **Editing third-party charts** — forked charts drifting from upstream; override via values, contribute fixes upstream.\n- **`--set` for complex config** — escaping hell; values files for anything non-trivial.\n- **Release name instability** — generated names breaking tooling; stable names per environment.\n- **Ignoring `helm test`** — no post-install verification; add smoke tests.\n- **Chart version vs appVersion confusion** — bumping the wrong one; chart version for chart changes, appVersion for the app.\n- **Storing charts in git without registry** — no immutability story; OCI registries for distribution.\n",{"name":5,"category":24,"description":7},"development","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-helm-pro",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill helm-pro",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill helm-pro",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill helm-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-helm-pro\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]