arch-event-driven
Installation
SKILL.md
One-line summary
Components communicate by emitting and reacting to events through a broker, not by calling each other directly. The producer doesn't know who consumes; the consumer doesn't know who produced.
When to use this skill
- Loosely-coupled components that must scale independently.
- Real-time data processing, streaming, or analytics pipelines.
- Business workflows where the steps are naturally "X happened, now Y reacts".
- Systems where downstream consumers are added or removed without the producer knowing.
When NOT to use this skill
- Strict transactional consistency requirements — events are eventually consistent.
- Synchronous request-response is the natural communication shape — forcing async adds latency and complexity.
- Small system with a handful of components that all live in one process — events are overkill; direct calls are simpler.