Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From queue-orchestrator
Designs and implements distributed systems patterns including consensus, leader election, and caching strategies.
How this command is triggered — by the user, by Claude, or both
Slash command
/queue-orchestrator:distributed <requirement> [focus]sonnetThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Distributed Command Distributed systems design and consensus patterns ## Arguments **$1 (Required)**: requirement **$2 (Optional)**: focus ## Examples Invoke the distributed-systems-expert agent with: $ARGUMENTS
Distributed systems design and consensus patterns
$1 (Required): requirement
$2 (Optional): focus
/distributed "Design distributed cache" consistency
/distributed "Implement leader election" consensus
Invoke the distributed-systems-expert agent with: $ARGUMENTS
npx claudepluginhub dotclaude/marketplace --plugin queue-orchestrator/distributedDesigns and analyzes distributed systems with CAP trade-offs, consensus protocols (Raft/Paxos), locking (Redlock/ZooKeeper), sharding, consistency patterns, and leader election. Outputs architecture docs, analysis files, and git commit with verdict. Supports focused flags.
/distributed-systems-designGuides distributed system design using a structured 4-step framework. Supports CHECKER mode for auditing existing designs and APPLIER mode for step-by-step design.
/designGuides through a bottom-up system-design workflow: clarify requirements, estimate scale, design with building blocks, weigh trade-offs, stress-test, and produce a diagram. Accepts a system name as argument.
/design-solutionSystem design combining multiple patterns (concurrency, state, reactive, etc.).
/architectGuides the user through production-grade systems design for a given task, covering requirements, architecture, failure modes, observability, and self-documenting code.
/architectGenerates system designs, authentication models, scalability plans, tech stacks, and team coordination as Principal Software Architect.