designing-distributed-system-tests

SKILLFlujo de trabajocomunidad
v0.0.0shenliMITActualizado hace 1 mFuente →

Use when designing a test plan for a distributed or stateful system — anything with persistence, replication, consensus, retries, idempotency, async messaging, multi-tenancy, or partial failure. Plans are claim-driven: investigate the product's claimed guarantees first, then design hypotheses and sc

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
228Estrellas del repo
1Clientes
1Formatos
hace 1 mÚltima actualización
Skill
Autorshenli
Versión0.0.0
LicenciaMIT
CategoríaFlujo de trabajo
Formatosskill.md
PromptNo publicado
Compatibilidad
Claude✓ Compatible
Cursor
Copilot
ChatGPT
Gemini
Acerca de

Use when designing a test plan for a distributed or stateful system — anything with persistence, replication, consensus, retries, idempotency, async messaging, multi-tenancy, or partial failure. Plans are claim-driven: investigate the product's claimed guarantees first, then design hypotheses and scenarios that try to falsify those claims under fault. Handles change-scoped plans (a commit / PR / f

Palabras clave
skillclaude