Event Sourcing
Store state as immutable event log instead of current values. Build auditable, event-driven systems with full history. Use when auditability, temporal queries, or event-driven processing matters.
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-sourcinggit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/data-architecture/skills/event-sourcing ~/.claude/skills/event-sourcingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Event Sourcing Build auditable systems by storing complete history of state changes as immutable events rather than current values. ## Context You are designing a system requiring auditability, temporal analysis, or replay capability. Event sourcing provides complete history and enables powerful event-driven architectures. Read domain requirements and existing event-driven patterns. ## Domain Context Based on Greg Young's event sourcing work and CQRS patterns: - **Event Store**: Append-only log of domain events; immutable, ordered - **Aggregate Reconstruction**: Replay events to reconstruct current state on-demand - **Snapshots**: Optimize replay by storing intermediate state; trade storage for speed - **Event Versioning**: Events evolve; handle schema changes in replays - **Projections**: Materialize different views from event stream (CQRS read models) ## Instructions 1. **Identify Core Events**: What state changes matter? Order placed, payment received, shipment dispatched. Each event is fact about domain; captured in past tense. 2. **Design Event Schema**: Each event contains timestamp, aggregate ID, type, data. Include enough context to understand intent (who, when, why). 3. **Plan Aggregate Boundaries**: Group related events into aggregates. Order aggregate: contains all events for single order. Enables consistent snapshots and replay.
Details
- Skill name
event-sourcing- Repository
- sethdford/claude-skills
- Path
architect/data-architecture/skills/event-sourcing/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Event Sourcing skill do?
Store state as immutable event log instead of current values. Build auditable, event-driven systems with full history. Use when auditability, temporal queries, or event-driven processing matters.
How do I install the Event Sourcing 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 Sourcing 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.
Experience Map
48sethdford/claude-skills
Create a holistic experience map showing the full ecosystem of user touchpoints, channels, and relationships.
Escaped Defect Analysis
48sethdford/claude-skills
Expert approach to escaped-defect-analysis in quality measurement. Use when working with .
Function Design
48sethdford/claude-skills
Designing pure functions with single purpose, minimal parameters, clear side effects, and high cohesion.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.