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.

48 stars 10 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill event-sourcing
Manual install
git 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-sourcing

Personal 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.
Read the full skill on GitHub

Details

Skill name
event-sourcing
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

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.