metalbear-co

Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed through the mirrord UI server's HTTP API. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate connection failures (reset, timed out, refused), test app behavior under degraded network conditions, or wire chaos rules into CI test runs. Always use this skill instead of the deprecated _experimental_.latency mirrord config option.

Helps users run multiple concurrent mirrord sessions from a single mirrord-up.yaml (compose-style multi-service local debugging). Use when the user mentions mirrord up, mirrord-up.yaml, mirrord up init, debugging several related microservices together, or managing multiple mirrord sessions' lifecycle in one command.

Helps users generate, edit, and validate mirrord.json configuration files for mirrord (MetalBear). Use when the user wants to connect their local process to a Kubernetes environment, configure features (env/fs/network), or needs feedback on an existing mirrord.json. Always ensures output JSON is valid and schema-conformant.

Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer wants to run "mirrord preview" ad hoc, or wire preview environments into CI with the metalbear-co/mirrord-preview GitHub Action (e.g. per-PR previews).

Helps DevOps engineers configure mirrord Operator's Kafka queue splitting feature end-to-end. Generates MirrordKafkaClientConfig and MirrordKafkaTopicsConsumer Kubernetes CRD YAMLs, the matching mirrord.json split_queues section, and Helm value guidance. Use this skill whenever the user mentions Kafka splitting with mirrord, MirrordKafkaClientConfig, MirrordKafkaTopicsConsumer, Kafka queue splitting, Kafka topic splitting, configuring mirrord with Kafka, setting up Kafka for mirrord operator, or troubleshooting Kafka splitting sessions. Also trigger when users mention split_queues with queue_type Kafka, or ask about connecting mirrord to a Kafka cluster. This is a Team/Enterprise feature of mirrord.

Help users set up mirrord in CI pipelines for testing against real Kubernetes environments. Use when users want to run end-to-end tests, integration tests, or automated tests in CI using mirrord to connect to staging/shared clusters.

Help users install and configure the mirrord operator for team environments. Use when users ask about operator setup, Helm installation, licensing, or multi-user mirrord deployments.

Guide users from zero to their first working mirrord session. Use when a user is new to mirrord, wants to install it, or needs help running their first session connecting to a Kubernetes cluster.

Use when a developer asks for a MetalMart shop change that must be implemented and verified end-to-end with local mirrord and Playwright before handoff.

Use when running one MetalMart shop service locally under mirrord against the playground GKE cluster. Requires Playwright UI verification for catalog or frontend-affecting changes, not curl alone.

Use when a developer asks for a MetalMart shop change that must be implemented and verified end-to-end in a mirrord preview environment with Playwright before handoff.

Use when a product manager asks for a MetalMart playground feature or code change and wants the full implementation workflow run through branch, PR, preview build, and preview handoff.

Use when a PM or developer wants a MetalMart shop change implemented, pushed to a PR, and exposed through the mirrord preview workflow for human review after the preview build succeeds.

Use when the user explicitly wants the current local git changes reviewed, committed on a new branch, pushed to origin, and opened as a pull request.

Use when the user wants the playground repo built and deployed to local minikube for testing, including changed service images, `overlays/local`, readiness checks, and local access URLs.

Validate Kubernetes manifests, Dockerfiles, Helm charts, and application code for both security and correctness. Enforces NEVER/ALWAYS rules across security domains and correctness domains so AI-generated code is shaped to fit a real Kubernetes environment.

Configure OpenTelemetry context propagation (OTEL_PROPAGATORS) for services running in Kubernetes, especially when using mirrord to intercept or steal traffic. Use this skill whenever the user mentions OTEL_PROPAGATORS, OpenTelemetry propagators, trace context headers, W3C tracecontext, B3 headers, distributed tracing setup, OTel auto-instrumentation configuration, or configuring header propagation for mirrord sessions. Also trigger when someone asks about traceparent headers, baggage propagation, connecting local dev tracing to a cluster, or ensuring downstream services see the correct trace context when traffic is intercepted by mirrord. This skill covers env vars, Kubernetes Instrumentation CRDs, docker-compose, Spring Boot properties, and local dev config for mirrord users.