14 skills · sorted by relevance
Plan controlled failure experiments to uncover system weaknesses. Define normal operating metrics, estimate affected users and reliability risk, set abort and recovery conditions, and turn experiment results into a structured review with follow-up actions.
Chaos engineering: hypothesis-driven fault injection to surface weakness before users do. Use when designing a chaos experiment, planning a gameday, choosing what to inject, computing blast radius, or building a chaos maturity model.
The English summary is being prepared. Showing the original description.
Decision framework for isolating every external dependency in a test suite: when to use in-process mocks, HTTP stubs (MSW, WireMock), record-replay, fault injection (Toxiproxy), or ephemeral real services (Testcontainers), and how to enforce that no real calls escape in CI. Use when: "mock service," "stub API," "fake service," "WireMock," "MSW," "Toxiproxy," "test isolation," "dependency management," "stub an external API in CI." Not for: consumer-driven contract verification (Pact, broker) — use contract-testing; standing up a full Docker Compose env or seed data — use test-environments; broad resilience/game-day fault campaigns — use chaos-engineering. Related: contract-testing, test-environments, api-testing, test-data-management, chaos-engineering.
The English summary is being prepared. Showing the original description.
Expert en chaos engineering (Gremlin, Litmus, fault injection, game days, fiabilité)
The English summary is being prepared. Showing the original description.
Define service reliability targets, choose measurements that reflect user experience, and calculate error budgets—the failures a target allows. Generate alert thresholds and review existing definitions for unrealistic targets, unclear metrics, and missing response policies.
Failure injection patterns, blast radius control, steady state hypothesis, and gameday planning for resilience testing.
The English summary is being prepared. Showing the original description.
Validate system resilience through controlled fault injection. Covers hypothesis-driven chaos experiments, failure injection types (network, service, infrastructure, dependency), LitmusChaos/Chaos Mesh/AWS FIS/Gremlin/toxiproxy tooling, automated abort gating, game day planning, and progressive chaos adoption. Use when: "chaos engineering," "fault injection," "resilience test," "game day," "failure recovery," "system reliability," "blast radius." Not for: safe rollout flags/canary/dark launch during a release — use testing-in-production; designing new tests from production telemetry — use observability-driven-testing. Related: testing-in-production, observability-driven-testing, performance-testing, release-readiness, test-environments.
The English summary is being prepared. Showing the original description.
Resilience testing specialist for failure injection, game day planning, and building confidence in system reliabilityUse when "chaos engineering, resilience testing, failure injection, game day, fault tolerance, chaos experiment, disaster recovery, reliability testing, chaos-engineering, resilience, failure-injection, game-day, fault-tolerance, reliability, testing, litmus, chaos-monkey, ml-memory" mentioned.
The English summary is being prepared. Showing the original description.
Audit existing resilience — identify untested failure modes and chaos engineering gaps. Use when asked "how resilient are we", "what failure modes are untested", or "find our chaos engineering gaps".
The English summary is being prepared. Showing the original description.
Design a chaos engineering experiment — hypothesis, blast radius, steady state, and abort conditions. Use when asked to "design a chaos experiment", "inject a failure", or "test the resilience of this service".
The English summary is being prepared. Showing the original description.
Design a game day — simulated failure scenario, runbook, and post-event review. Use when asked to "run a game day", "plan a failure drill", or "simulate an outage".
The English summary is being prepared. Showing the original description.
Provides chaos engineering best practices for resilience testing, fault injection, and game day planning. Use when designing resilience experiments, configuring chaos tools, planning game days, or when user mentions 'chaos engineering', 'resilience', 'litmus', 'game day', 'fault injection', 'chaos monkey', 'blast radius', 'steady state', 'failure mode'.
The English summary is being prepared. Showing the original description.
Design and execute chaos engineering experiments using Litmus or Chaos Mesh. Test system resilience through controlled fault injection, validate hypothesis-driven tests, and improve failure recovery. Use before major product launches, after architecture changes to validate resilience, during GameDays or disaster recovery drills, to validate assumptions about failure modes, or as part of an SRE maturity program.
The English summary is being prepared. Showing the original description.
Chaos Engineering discipline — proactive experimentation on distributed systems to build confidence in their resilience. Covers Netflix-inspired chaos principles, experiment design, blast radius control, LitmusChaos and Chaos Mesh usage, game day planning, and production safety. USE WHEN: validating system resilience before production incidents, designing chaos experiments, planning game days, implementing CI/CD chaos pipeline, or building confidence in fault tolerance. Triggers on "chaos engineering", "chaos experiment", "game day", "resilience test", "fault injection", "Litmus", "Chaos Mesh", "break things on purpose".
The English summary is being prepared. Showing the original description.