Event Driven Architecture
Design systems that communicate through events instead of direct service calls. Use when building loosely-coupled, scalable, and resilient architectures.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill event-driven-architecturegit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/system-design/skills/event-driven-architecture ~/.claude/skills/event-driven-architecturePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Event-Driven Architecture Build systems where services communicate through immutable events, enabling loose coupling and independent scaling. ## Context You are designing an event-driven system. The user is building integrations across services or needs to decouple components. Read their current architecture and integration patterns. ## Domain Context Based on Gregor Hohpe's Enterprise Integration Patterns and modern event-driven research: - **Event Sourcing**: Store state as append-only event log; reconstruct state by replaying events - **Event Bus**: Central publish-subscribe; services emit domain events, others react independently - **Choreography vs Orchestration**: Choreography = services react to events independently; orchestration = central coordinator directs flow - **Exactly-Once Semantics**: Guarantee each event is processed once; requires deduplication at consumer - **Event Versioning**: Events evolve over time; old and new consumers must coexist ## Instructions 1. **Define Events**: For each business process, identify events (UserCreated, OrderPlaced, PaymentProcessed). Include: timestamp, aggregate ID, payload, version. 2. **Design Producer & Consumer**: For each service that publishes events, specify topic/channel. For consumers, specify subscription and reaction. Include idempotency key for deduplication.
Details
- Skill name
event-driven-architecture- Repository
- sethdford/claude-skills
- Path
architect/system-design/skills/event-driven-architecture/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Event Driven Architecture skill do?
Design systems that communicate through events instead of direct service calls. Use when building loosely-coupled, scalable, and resilient architectures.
How do I install the Event Driven Architecture skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Event Driven Architecture popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Functional Patterns
48sethdford/claude-skills
Higher-order functions, composition, monads, immutability, and functional programming idioms.
Design Critique
48sethdford/claude-skills
Facilitate structured design critiques with clear feedback frameworks and actionable outcomes.
Go to Market Strategy
48sethdford/claude-skills
Launch and go-to-market skill for product managers.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.