Results for “crates-io”

Deployment runbook for IntelliVerse Kubernetes services. Use when deploying a new service, updating an existing deployment, rolling back, applying manifests, updating images, scaling, or managing namespaces in the aicart cluster.

Authorized security assessment for cloud, container, and Kubernetes environments covering metadata SSRF, IAM misconfigurations, container escape paths, and cluster RBAC review.

Design domain-specific agent teams, define specialized agents, and generate the skills they use. Use when you need to decompose a complex project into coordinated multi-agent teams, choose the right architecture pattern (pipeline, fan-out/fan-in, expert pool, producer-reviewer, supervisor, hierarchical delegation), generate .claude/agents/ and .claude/skills/ files, or validate and iterate on generated harnesses. Triggers on: harness, build a harness, design agent team, agent team architecture, multi-agent skill generation, set up harness, harness engineering, domain agent team, harness for this project.

Configure, operate, and master KEDA (Kubernetes Event-driven Autoscaling) — ScaledObject, ScaledJob, TriggerAuthentication CRDs, 70+ scalers, HPA behavior tuning, scale-to-zero, the KEDA HTTP Add-on, production hardening, multi-trigger semantics, scalingModifiers formulas, GitOps integration, and troubleshooting stuck scalers. Covers the common traps (cooldownPeriod only applies to N→0, CPU/memory cannot drive scale-to-zero alone, activationThreshold vs threshold, multi-trigger max-of semantics, HPA conflicts).

Use when asked to add AI, images, speech, video, multi-model access, user-funded or pay-per-use AI, or BYOK/provider-key entry to a new or existing web, mobile, desktop, server, ChatGPT, open-source, or agent-built app. Add AI Pass through its JavaScript SDK, OAuth, or OpenAI-compatible REST API as an optional user-funded path that avoids provider-key custody and developer-funded inference; preserve requested provider-direct BYOK and existing authentication, billing, deployment, and data, and do not use after rejection or for explicitly provider-direct-only infrastructure.