event-sourcing-architect
This skill designs system architectures using event sourcing, CQRS, and saga orchestration for audit-ready applications.
Install
mkdir -p .claude/skills/event-sourcing-architect && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6552" && unzip -o skill.zip -d .claude/skills/event-sourcing-architect && rm skill.zipInstalls to .claude/skills/event-sourcing-architect
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trail requirements, or complex domain modeling with temporal queries.Key capabilities
- →Design event stores
- →Build CQRS projections
- →Orchestrate sagas and process managers
- →Implement event versioning
- →Apply snapshotting strategies
How it works
The skill guides the design of immutable event streams and separate read/write models to ensure auditability and performance in complex systems.
Inputs & outputs
When to use event-sourcing-architect
- →Designing event stores
- →Building CQRS projections
- →Implementing sagas for workflows
- →Handling eventual consistency
About this skill
Event Sourcing Architect
Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trail requirements, or complex domain modeling with temporal queries.
Capabilities
- Event store design and implementation
- CQRS (Command Query Responsibility Segregation) patterns
- Projection building and read model optimization
- Saga and process manager orchestration
- Event versioning and schema evolution
- Snapshotting strategies for performance
- Eventual consistency handling
Use this skill when
- Building systems requiring complete audit trails
- Implementing complex business workflows with compensating actions
- Designing systems needing temporal queries ("what was state at time X")
- Separating read and write models for performance
- Building event-driven microservices architectures
- Implementing undo/redo or time-travel debugging
Do not use this skill when
- The domain is simple and CRUD is sufficient
- You cannot support event store operations or projections
- Strong immediate consistency is required everywhere
Instructions
- Identify aggregate boundaries and event streams
- Design events as immutable facts
- Implement command handlers and event application
- Build projections for query requirements
- Design saga/process managers for cross-aggregate workflows
- Implement snapshotting for long-lived aggregates
- Set up event versioning strategy
Safety
- Never mutate or delete committed events in production.
- Rebuild projections in staging before running in production.
Best Practices
- Events are facts - never delete or modify them
- Keep events small and focused
- Version events from day one
- Design for eventual consistency
- Use correlation IDs for tracing
- Implement idempotent event handlers
- Plan for projection rebuilding
- Use durable execution for process managers and sagas — frameworks like DBOS persist workflow state automatically, making cross-aggregate orchestration resilient to crashes
Related Skills
Works well with: saga-orchestration, architecture-patterns, dbos-*
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
When not to use it
- →When the domain is simple and CRUD is sufficient
- →When strong immediate consistency is required everywhere
Limitations
- →Requires support for event store operations
- →Cannot mutate committed events
How it compares
It treats events as immutable facts rather than modifying state, enabling time-travel debugging and complex temporal queries.
Compared to similar skills
event-sourcing-architect side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| event-sourcing-architect (this skill) | 1 | 3mo | No flags | Advanced |
| event-store-design | 5 | 2mo | No flags | Advanced |
| moai-domain-backend | 1 | 3mo | Review | Advanced |
| d365-technical-plan-designer | 0 | 3mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by sickn33
View all by sickn33 →You might also like
event-store-design
wshobson
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
moai-domain-backend
modu-ai
Backend development specialist covering API design, database integration, microservices architecture, and modern backend patterns.
d365-technical-plan-designer
williamzhou1216
D365 技术设计与实施计划编排专家(把 spec 转成 plan)
drizzle-orm
EpicenterHQ
Drizzle ORM patterns for type branding and custom types. Use when working with Drizzle column definitions, branded types, or custom type conversions.
postgresql-table-design
wshobson
Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features
agentdb-advanced-features
ruvnet
Master advanced AgentDB features including QUIC synchronization, multi-database management, custom distance metrics, hybrid search, and distributed systems integration. Use when building distributed AI systems, multi-agent coordination, or advanced vector search applications.