Individual skill
cqrs-event-sourcing-designer
Designs Command Query Responsibility Segregation (CQRS) and Event Sourcing models with projection rebuilders.
skills/architecture/cqrs-event-sourcing-designer/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 625 bytesSKILL.mdcore · 1,781 bytesexamples/example.mddoc · 1,163 bytes
Read excerpt
## Purpose
Architect Command Query Responsibility Segregation (CQRS) and Event Sourcing (ES) systems, separating write-side domain command handling from read-side materialized view projections with full auditability.
## When to Use
- High-compliance domains requiring immutable audit logs (Fintech, Healthcare, Legal, Supply Chain).
- Systems with asymmetric read/write ratios and complex reporting queries.
- Designing collaborative workspaces with branch/merge or time-travel history.
## What to Analyze
1. **Command vs Query Separation**: Command handlers (validate and emit events) vs Query handlers (read denormalized projections).
2. **Event Store Architecture**: Append-only immutable log (`aggregate_id`, `version`, `event_type`, `payload`) with optimistic concurrency control.