event-driven-architecture

SKILL.md

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 as First-Class Citizens Events represent immutable facts that have occurred in the system. Use past tense naming (OrderCreated, PaymentProcessed) and include all necessary context.

Eventual Consistency Systems achieve consistency over time rather than immediately. Trade strong consistency for higher availability and scalability.

Event-driven architecture patterns with event sourcing, CQRS, and message-driven communication. Use when designing distributed systems, microservices communication, or systems requiring eventual consistency and scalability. Source: nickcrew/claude-ctx-plugin.

View raw