Backend Event Sourcing
Use when the user asks about event sourcing, storing every change as an append-only event log, event store, rehydrating aggregates, snapshots, upcasting or projection rebuilds. Produces an event-sourced aggregate and store design. Not for CQRS without event sourcing (use backend-cqrs-patterns).
Install
npx skills add j4flmao/agent-skills --skill backend-event-sourcinggit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/backend/universal/event-sourcing ~/.claude/skills/backend-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
# Backend Event Sourcing
## Purpose
Store state changes as an append-only sequence of events. Current state is derived by replaying events. Every event is immutable, auditable, and replayable.
## Agent Protocol
### Trigger
Exact user phrases: "event sourcing", "event store", "event stream", "event sourced", "rehydrate from events", "event replay", "projection rebuild", "append-only log", "event history", "event store pattern".
### Input Context
- Domain aggregates and their state changes.
- Event store technology (PostgreSQL, EventStoreDB, DynamoDB).
- Projection requirements (read models, search indexes, materialized views).
### Output Artifact
Event sourcing design as text. No file unless requested.
### Response Format
```
Aggregate: {name}
Events: [{EventName, version, key fields}]
Current state: {derived by replay}
Projections: [{name, rebuild from}]
```
### Completion Criteria
- [ ] All state changes are captured as events (not just some).
- [ ] Event store is append-only — no updates or deletes.
- [ ] Aggregate state can be rebuilt by replaying all events.
- [ ] Projections can be rebuilt from scratch by replaying all events.
- [ ] Events are immutable and carry version number.
- [ ] Event schema includes metadata (eventId, aggregateId, version, timestamp).
- [ ] Snapshot strategy defined for aggregates with many events.
### Max Response Length
Per aggregate: 8 lines. Full design: 35 lines.
## Architecture Decision Tree
### Should I Use Event Sourcing?Details
- Skill name
backend-event-sourcing- Repository
- j4flmao/agent-skills
- Path
skills/backend/universal/event-sourcing/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Backend Event Sourcing skill do?
Use when the user asks about event sourcing, storing every change as an append-only event log, event store, rehydrating aggregates, snapshots, upcasting or projection rebuilds. Produces an event-sourced aggregate and store design. Not for CQRS without event sourcing (use backend-cqrs-patterns).
How do I install the Backend Event Sourcing skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill backend-event-sourcing. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Backend Event Sourcing popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Backend Feature Flags
45j4flmao/agent-skills
Use when the user asks about server-side feature flags, kill switches, percentage rollouts, OpenFeature, LaunchDarkly, Unleash, Flagsmith or flag cleanup. Produces a flag design with ownership, defaults and evaluation code. Not for client UI flags (use frontend-feature-flags) or deploy strategies (use progressive-delivery).
Backend Event Driven
45j4flmao/agent-skills
Use when the user asks about event-driven architecture, domain vs integration events, publishing events between services, Kafka or RabbitMQ consumers, event schema versioning, DLQs or sagas. Produces event catalog, topology and consumer code. Not for event stores (use backend-event-sourcing) or broker operations (use backend-message-queue).
Backend File Storage
45j4flmao/agent-skills
Use when the user asks about file uploads, S3 presigned URLs, direct-to-storage uploads, object keys, Azure Blob or GCS, CDN delivery of files, virus scanning or lifecycle policies. Produces an upload and storage design with validation. Not for CSV data imports (use backend-bulk-import).
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.