From nickcrew-claude-ctx-plugin
Guides event-driven architecture with event sourcing, CQRS, sagas, message brokers for distributed systems, microservices, scalability, and eventual consistency.
npx claudepluginhub nickcrew/claude-cortexThis skill uses the workspace's default tool permissions.
Expert guidance for designing, implementing, and operating event-driven systems with proven patterns for event sourcing, CQRS, message brokers, saga coordination, and eventual consistency management.
Guides implementation of event-driven architecture using domain events, event sourcing, CQRS, outbox patterns, and message brokers for decoupled, reliable systems.
Designs event-sourced systems using CQRS, event stores, projections, sagas, and eventual consistency patterns. Useful for audit trails, temporal queries, and complex workflows.
Provides microservices architecture patterns for service boundaries, inter-service communication, data management, resilience, service discovery, and event-driven designs. Use for monolith decomposition and distributed systems.
Share bugs, ideas, or general feedback.
Expert guidance for designing, implementing, and operating event-driven systems with proven patterns for event sourcing, CQRS, message brokers, saga coordination, and eventual consistency management.
Events represent immutable facts that have occurred in the system. Use past tense naming (OrderCreated, PaymentProcessed) and include all necessary context.
Systems achieve consistency over time rather than immediately. Trade strong consistency for higher availability and scalability.
Services communicate through events without direct dependencies, enabling independent evolution and deployment.
Operations don't block waiting for responses, improving system responsiveness and resilience.
Design around what happened (events) rather than what to do (commands).
| Topic | Load reference |
|---|---|
| Event structure, types, and characteristics | skills/event-driven-architecture/references/event-fundamentals.md |
| Event sourcing pattern and implementation | skills/event-driven-architecture/references/event-sourcing.md |
| CQRS pattern with read/write separation | skills/event-driven-architecture/references/cqrs.md |
| Message brokers (RabbitMQ, Kafka, SQS/SNS) | skills/event-driven-architecture/references/message-brokers.md |
| Saga pattern for distributed transactions | skills/event-driven-architecture/references/saga-pattern.md |
| Choreography vs orchestration patterns | skills/event-driven-architecture/references/choreography-orchestration.md |
| Eventual consistency and conflict resolution | skills/event-driven-architecture/references/eventual-consistency.md |
| Best practices, anti-patterns, testing | skills/event-driven-architecture/references/best-practices.md |