LeoYeAI/agent-master-skills / skills/backend-event-stores
event-store
VerifiedDesign and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, implementing event persistence, projections, snapshotting, or CQRS patterns.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 2.1 KB |
| SKILL.md | skill md | 16.3 KB |
| _meta.json | config | 291 B |
README.md
View on GitHub# Event Store
Guide to designing event stores for event-sourced applications — covering event schemas, projections, snapshotting, and CQRS integration.
## What's Inside
- Event Store Architecture — streams, global position, requirements
- Technology Comparison — EventStoreDB, PostgreSQL, Kafka, DynamoDB
- Event Schema Design — envelope structure, schema evolution rules
- PostgreSQL Event Store Schema — events, snapshots, subscription checkpoints
- Event Store Implementation — append with optimistic concurrency, read stream, read all (Python)
- Projections — lifecycle, idempotent handlers, design rules, projection example
- Snapshotting — snapshot flow, aggregate rehydration optimization
- CQRS Integration — write/read separation, command handler pattern
- EventStoreDB Integration example (Python)
- DynamoDB Event Store Implementation with single-table design
## When to Use
- Designing event sourcing infrastructure
- Choosing between event store technologies
- Implementing custom event stores
- Building projections from event streams
- Adding snapshotting for aggregate performance
- Integrating CQRS with event sourcing
## Installation
```bash
npx add https://github.com/wpank/ai/tree/main/skills/backend/event-store
```
### Manual Installation
#### Cursor (per-project)
From your project root:
```bash
mkdir -p .cursor/skills
cp -r ~/.ai-skills/skills/backend/event-store .cursor/skills/event-store
```
#### Cursor (global)
```bash
mkdir -p ~/.cursor/skills
cp -r ~/.ai-skills/skills/backend/event-store ~/.cursor/skills/event-store
```
#### Claude Code (per-project)
From your project root:
```bash
mkdir -p .claude/skills
cp -r ~/.ai-skills/skills/backend/event-store .claude/skills/event-store
```
#### Claude Code (global)
```bash
mkdir -p ~/.claude/skills
cp -r ~/.ai-skills/skills/backend/event-store ~/.claude/skills/event-store
```
## Related Skills
- `architecture-patterns` — Clean Architecture and DDD foundations for event sourcing
- `microservices-patterns` — Saga pattern and distributed transactions with events
---
Part of the [Backend](..) skill category.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |