kubernetes
Kubernetes manifests, Helm charts, scaling strategies, service mesh, and cluster management
Kubernetes manifests, Helm charts, scaling strategies, service mesh, and cluster management
Explicitly save a memory to the UltraThink persistent brain
"Expert hybrid cloud architect specializing in complex multi-cloud"
Prometheus, Grafana, alerting, SLOs, structured logging, distributed tracing, and observability patterns
读取当前鼠标坐标、查看显示器边界、通过本地 helper 服务执行点击/按键/应用切换,并把鼠标向指定边缘推进或连续扫动;适用于扩展屏、Sidecar 和固定坐标演示前的录点与指针定位。
Create a new meter or charger integration for the EVSE Load Balancer
用于 soarmMoce 的 DJI 展示演示流程。优先覆盖五个展示入口:1) 用户说生成轨迹、沿轨迹运动一下再复位时,直接走 `trajectory-demo`;2) 用户说启动 Pocket 3 录像并按刚才轨迹完成拍摄后停止录像时,直接走 `trajectory-record`;3) 用户说打开最近在看的书时,直接走 `books-open-recent`;4) 用户说向后翻页时,直接走 `books-next-page`;5) 用户要求连续拍现场活动照片、维护最喜欢的 10 张,并继续逐张讲解/修图时,走下方“现场活动拍照 demo”流程。除此之外,拍照时先做展示动作再回 home 然后调用 Photo Booth 拍照;P 图/海报时使用最近一张已保存照片;方向微调用 `frame=user` 的笛卡尔 `dx/dy/dz`;单独说执行轨迹时可只跑 `trajectory`;回 Home 时直接执行 `home`。
Deploys a complete monitoring stack with Prometheus, Grafana, and Node Exporter using Docker Compose.
Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or...
Create a new track with specification and phased implementation plan
Instrument applications with Azure Monitor and OpenTelemetry for JavaScript (@azure/monitor-opentelemetry). Use when adding distributed tracing, metrics, and logs to Node.js applications with Appli...
Set up affiliate conversion tracking with UTM parameters and link tagging. Triggers on: "set up tracking", "create UTM links", "track my affiliate links", "tracking pixels", "click attribution", "organize my links", "UTM parameters", "tag my links", "campaign tracking", "link tracking setup", "prepare for launch", "debug attribution", "tracking spreadsheet".
OpenTelemetry instrumentation for Node.js — traces, metrics, spans, exporters (Jaeger, Honeycomb, Grafana), auto-instrumentation, and Next.js integration
Classify workflow failures and attempt automatic recovery. Use when sprint/feature fails during implementation to determine if auto-fix is possible or manual intervention required.
Structured approach for implementing architect-provided plans through controlled batch execution with review checkpoints - execute in batches (default 3 tasks), verify each step, stop on blockers; don't force through blockers
Set up hierarchical Intent Layer (AGENTS.md files) for codebases. Use when initializing a new project, adding context infrastructure to an existing repo, user asks to set up AGENTS.md, add intent layer, make agents understand the codebase, or scaffolding AI-friendly project documentation.
Expertise in deploying the project to a target environment. Use when the user asks to "deploy", "release", or "push to prod".
Deploys features to staging environment with database migrations, health checks, and deployment verification. Use during /ship-staging phase or when deploying to staging environments for validation before production release.
Validates cross-artifact consistency and detects breaking changes during feature analysis. Use when running /analyze command, validating spec-plan alignment, checking task-implementation consistency, or identifying API/database/UI breaking changes before deployment. (project)
Completes feature/epic workflows after deployment with comprehensive walkthrough generation for epics (v5.0+), roadmap updates, artifact archival, documentation, and branch cleanup. Use after /ship-prod, /deploy-prod, or /build-local completes, or when user asks to finalize. (project)
Validates production readiness through performance benchmarking, accessibility audits, security reviews, and code quality checks. Use after implementation phase completes, before deployment, or when conducting quality gates for features. (project)
Executes production deployment workflow by promoting validated staging builds to production with semantic versioning, health checks, and release tagging. Use when running /ship-prod command, deploying to production after staging validation, or promoting staging builds to production environment.
Executes implementation tasks using Test-Driven Development, prevents code duplication through anti-duplication checks, and maintains quality through continuous testing. Use when implementing features from tasks.md, during the /implement phase, or when the user requests TDD-based implementation. (project)