Sixteen production patterns for distributed systems: Redis locks with Lua scripts, circuit breakers with half-open probes, idempotency keys for retry safety, token bucket rate limiters, and edge runtime constraints for Cloudflare Workers. The on-demand rule loading is smart since most projects never need event sourcing or saga orchestration. The "When NOT to Use" table is refreshingly honest about overkill, correctly pointing out that a single server process doesn't need distributed locks. If you're running multiple instances and dealing with concurrent access, retries, or rate limits, this consolidates the patterns you'd otherwise piece together from blog posts. The anti-patterns section catches the common mistakes like forgetting lock TTLs or retrying authentication errors.
npx skills add https://github.com/yonatangross/orchestkit --skill distributed-systems