Results for “helm”

Expert DevOps engineer for CI/CD, IaC, Kubernetes, and deployment automation. Activate on: CI/CD, GitHub Actions, Terraform, Docker, Kubernetes, Helm, ArgoCD, GitOps, deployment pipeline, infrastructure as code, container orchestration. NOT for: application code (use language skills), database schema (use data-pipeline-engineer), API design (use api-architect).

The English summary is being prepared. Showing the original description.

Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.

The English summary is being prepared. Showing the original description.

Use when the user wants the full package on a repo, says run my project workflow, project check-in, or is overwhelmed opening an old or new folder. Runs the project onboarding checklist—explain-new-project, project-worth-my-time, and project-catch-up—in order or on demand.

The English summary is being prepared. Showing the original description.

Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.

The English summary is being prepared. Showing the original description.

Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.

The English summary is being prepared. Showing the original description.

Kubernetes deployment workflow for container orchestration, Helm charts, service mesh, and production-ready K8s configurations.

The English summary is being prepared. Showing the original description.

NVIDIA RAG Blueprint deployment, configuration, troubleshooting, and shutdown guidance for Docker, Helm, and library-based RAG stacks.

The English summary is being prepared. Showing the original description.

Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.

The English summary is being prepared. Showing the original description.

Productivity analyst that maps your workflow, scores tasks, and builds a prioritized automation plan. Use when: (1) "audit my workflow", "what should I automate?", "productivity review", (2) Starting a new project and need to identify high-leverage tasks, (3) Feeling overwhelmed and need to prioritize, (4) After /compounder surfaces new friction or patterns. Reads compounder insights when available. Outputs to system/audit-report.md.

The English summary is being prepared. Showing the original description.

Productivity analyst that maps your workflow, scores tasks by time cost and energy drain, and builds a prioritized 4-week automation plan. Use when you want to audit your workflow, figure out what to automate, do a productivity review, identify high-leverage tasks, feel overwhelmed and need to prioritize, or after the compounder surfaces new friction. Part of the architect-system loop. Outputs to system/audit-report.md.

The English summary is being prepared. Showing the original description.

bu skill covers implementing automated security scanning for Infrastructure as Code (IaC) templates using tools like Checkov, tfsec, and KICS. It addresses Tespit etme misconfigurations in Terraform, CloudFormation, Kubernetes manifests, and Helm charts before Dağıt:ment, establishing policy-based governance, and integrating IaC scanning into CI/CD pipelines to prevent insecure cloud resource provisioning.

The English summary is being prepared. Showing the original description.

Use when arranging the project quality-check or investigating a concrete unresolved code concern

The English summary is being prepared. Showing the original description.

Use when independent bounded tasks benefit from delegation during implementation

The English summary is being prepared. Showing the original description.

Use when implementing any feature or bugfix, before writing implementation code

The English summary is being prepared. Showing the original description.

フロントエンド実装時に使用。コーディング規約準拠。コンポーネント設計。

The English summary is being prepared. Showing the original description.

Use when a multi-step change needs explicit sequencing, dependencies, or a handoff

The English summary is being prepared. Showing the original description.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

The English summary is being prepared. Showing the original description.

Use when recurring process failures, obsolete rules, or an explicit user request call for harness improvement.

The English summary is being prepared. Showing the original description.

開発サーバー・E2E・ブラウザ検証時に使用。既存プロセスを停止してからプロジェクト指定ポートで起動し、作業後に必ず停止する。

The English summary is being prepared. Showing the original description.

実装前に呼ぶ。High/Medium リスク変更のテストオラクル（期待値の根拠）とファルシフィケーション項目を定義する。

The English summary is being prepared. Showing the original description.

マージ前に必ず実行。静的チェック・テスト・体制レビュー（変更内容で決まる統合レビュアー＋反証型QA＋専門家最大1体、基本1サイクル）と追加テスト（test-recommendation）を実施し、通過後のみmainへのマージ・直接pushが可能。

The English summary is being prepared. Showing the original description.

バックエンド実装時に使用。DRY原則遵守。コーディング規約準拠。

The English summary is being prepared. Showing the original description.

作業開始時に使用。mainブランチでの作業禁止。Issue先行作成必須。

The English summary is being prepared. Showing the original description.

UI実装後の検証時に使用。agent-browser CLIでブラウザ上の動作を手動検証する。「UIを確認」「画面テスト」と言われたら使用（プロジェクトの E2E スイート実行は quality-check Step 5（推奨度・範囲で自動実施または確認）/ server-startup が担当）。

The English summary is being prepared. Showing the original description.