managing-infra
Infrastructure patterns for Kubernetes, Terraform, Helm, Kustomize, and GitHub Actions. Use when making K8s architectural decisions, choosing between Helm vs Kustomize, structuring Terraform modules, writing CI/CD workflows, or applying security best practices.
What this skill does
# Infrastructure Patterns ## When to Use What | Tool | Use For | | ------------------ | --------------------------------------------------- | | **Raw K8s YAML** | Simple deployments, one-off resources | | **Kustomize** | Environment variations, overlays without templating | | **Helm** | Complex apps, third-party charts, heavy templating | | **Terraform** | Cloud resources, infrastructure lifecycle | | **GitHub Actions** | CI/CD, automated testing, releases | | **Makefile** | Build automation, self-documenting targets | | **Dockerfile** | Container builds, multi-stage, multi-arch | ## Quick Decisions **Kustomize** when: Simple env differences, readable manifests, patching YAML **Helm** when: Complex templating, third-party charts, release management ## K8s Security Defaults Every workload: non-root user, read-only filesystem, no privilege escalation, dropped capabilities, network policies. ## GitHub Actions Patterns - **CI workflow**: Lint, test, compile on PRs (run on both x86 + ARM) - **Release workflow**: Multi-arch Docker build on tags (native ARM runners) - Pin actions by SHA, least-privilege permissions ## References - [KUBERNETES.md](KUBERNETES.md) - K8s resource patterns - [TERRAFORM.md](TERRAFORM.md) - Terraform module patterns - [GITHUB-ACTIONS.md](GITHUB-ACTIONS.md) - CI/CD workflow patterns - [MAKEFILE.md](MAKEFILE.md) - Build automation patterns - [DOCKERFILE.md](DOCKERFILE.md) - Container build patterns - [templates/](templates/) - Ready-to-use templates ## Commands ```bash kubectl apply -k ./ # Apply kustomize helm upgrade --install NAME . # Install/upgrade chart terraform plan && terraform apply ``` --- ## Gotchas - **Terraform state lock contention**: default 10-min lock timeout; bumped timeout doesn't help if the lock holder hung — force-unlock only after confirming the process is dead. - **Helm release name reuse on uninstalled-but-not-purged release** fails install with "already exists" — use `--no-hooks` + explicit purge, or never reuse names. - **Kustomize patches that match nothing silently produce empty diffs** — verify with `kustomize build` after every patch addition. - **Terraform `for_each` over a computed value forces apply-time count** — can cause spurious re-creation of resources between plans. - **`helm upgrade --install` on a changed values schema** can silently drop fields that no longer match — diff the rendered output, not just the values file. - **`kubectl apply --server-side` vs client-side conflicts** when both have been used: client-side last-applied-config can shadow server-side managed fields without error.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.