helm-practices
# Helm Best Practices
What this skill does
# Helm Best Practices This skill provides Helm chart development and maintenance patterns. ## When to Use Activates when: - Working with Helm charts - Modifying Chart.yaml dependencies - Updating Helm values - Deploying applications with Helm ## Dependency Management ### Critical Rules **Always use `helm dependency update`** - NOT `helm dependency build` ```bash # Correct helm dependency update # Wrong - Don't use this helm dependency build ``` **After changing Chart.yaml dependencies:** 1. Run `helm dependency update` to fetch updated dependencies 2. Run `make check-deps` before committing changes 3. Pre-commit hooks automatically rebuild dependencies ### Common Workflow ```bash # 1. Modify Chart.yaml vim Chart.yaml # 2. Update dependencies helm dependency update # 3. Check dependencies make check-deps # 4. Commit changes (pre-commit hook runs automatically) git add Chart.yaml Chart.lock charts/ git commit -m "update helm dependencies" ``` ## Helm Commands ### Testing Charts ```bash # Template and check output helm template <release-name> <chart-path> # Template with specific values helm template <release-name> <chart-path> -f values.yaml # Dry-run install helm install <release-name> <chart-path> --dry-run --debug ``` ### Debugging ```bash # Check current values helm get values <release-name> # Check all computed values helm get values <release-name> --all # Get manifest helm get manifest <release-name> ``` ## Best Practices ### Chart Structure - Keep templates focused and modular - Use helpers (`_helpers.tpl`) for repeated logic - Document all values in `values.yaml` with comments - Use semantic versioning for chart versions ### Values Organization - Use nested structures for related values - Provide sensible defaults - Document required vs optional values - Use `.Values` consistently ### Dependency Management - Pin dependency versions explicitly - Use repository URLs, not local paths in production - Keep `Chart.lock` in version control - Run `make check-deps` before committing ## Common Gotchas ❌ **Don't:** - Use `helm dependency build` (use `update` instead) - Forget to run `make check-deps` before committing - Commit without running pre-commit hooks - Hard-code values that should be configurable ✅ **Do:** - Use `helm dependency update` for dependency changes - Run `make check-deps` as part of your workflow - Let pre-commit hooks rebuild dependencies automatically - Make values configurable and well-documented
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.