event-store-design Skill (wshobson) for Claude: What It Does and How to Install It

Helps Claude design event stores for event-sourced systems, with a technology comparison and Postgres, Python, EventStoreDB and DynamoDB templates.

Installs: 11K; on skills.sh
Stars: 42.1K; on GitHub
Files: 1; besides SKILL.md
Updated: Oct 2026; last repo commit

This is a design guide for Claude, from wshobson's agents collection. SKILL.md covers the store architecture (streams, events, global position), five requirements, a technology comparison table and do and don't lists. references/details.md holds four templates: a PostgreSQL schema, a Python implementation, EventStoreDB usage and a DynamoDB store.

It loads when you design event sourcing infrastructure, choose a store technology or implement event persistence. It bundles no scripts. It needs your own database or service to run the code.

Good for

Backend engineers building an event-sourced system
Architects choosing between Postgres, EventStoreDB, Kafka, DynamoDB and Marten
Teams adding streams, snapshots and subscriptions to an existing store

Install event-store-design

Claude Code

Copy this prompt.

Install the event-store-design skill in Claude Code. Run this command:

/plugin marketplace add wshobson/agents
/plugin install backend-development@claude-code-workflows

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Pick one route. The plugin routes install the whole backend-development plugin: 8 agents, 1 command and 9 skills (counted from the plugin folder in the repo tree, which has no hooks or MCP config files). The skills-only routes install just this skill, with no agents or commands. The skill needs a store of your own to run the templates against.

From the project README. Source.

What's in the skill

When it loads

Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.

Sections in SKILL.md

When to Use This Skill
Core Concepts
1. Event Store Architecture
2. Event Store Requirements
Technology Comparison
Templates and detailed worked examples
Best Practices
Do's
Don'ts

Key facts

Author: wshobson (repo owner)
License: MIT
Installs on skills.sh: 11,030 (Nov 2, 2026)
GitHub stars: 42,081 for the whole wshobson/agents repo (Nov 2, 2026)
Last repo commit: Oct 30, 2026
What it includes: 2 files including SKILL.md: references/details.md holds the 4 templates (no scripts)
Needs: A database or service of your own for the templates: PostgreSQL (asyncpg), EventStoreDB (esdbclient) or DynamoDB (boto3)
Part of: The backend-development plugin in wshobson/agents. Counted from the plugin folder: 8 agents, 1 command and 9 skills
Works in: Claude Code, Codex CLI, Cursor, OpenCode, Antigravity CLI, GitHub Copilot and Pi, per the README. Skills-only installers ask which tool you use

What it includes

Streams of events per aggregate, plus a global position
Explains how streams, events and global ordering fit together.
Try: “Design an event store for orders with per-stream versions.”
Read · Event store architecture
Append-only, ordered, versioned, subscriptions, idempotent
A table says what each requirement means, such as optimistic concurrency for versioning.
Read · Five store requirements
EventStoreDB, PostgreSQL, Kafka, DynamoDB, Marten
Lists what each is best for and its limits, for example Kafka is not ideal for per-stream queries.
Read · Technology comparison
Events, snapshots and subscription_checkpoints tables
SQL with indexes on stream id and version, global position, event type and created time.
Write · Template 1: PostgreSQL schema
An asyncpg based implementation
Python classes that append and read events against a PostgreSQL pool.
Write · Template 2: Python event store
Python client example using esdbclient
Connects to a database at esdb://localhost:2113 in the example.
Write · Template 3: EventStoreDB usage
A boto3 based event store
Uses boto3 and the DynamoDB resource API.
Write · Template 4: DynamoDB store
Stream ids with aggregate type, correlation ids, never edit events
Includes versioning events from day one, idempotency by event id and not updating or deleting events.
Read · Do's and don'ts

From the official docs

Permissions

Low risk

The main risk is that generated schema and storage code runs against a real database. Try it on a development database and review the SQL first.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

Templates create tables and connect to databases
details.md has CREATE TABLE and CREATE INDEX statements and clients for PostgreSQL, EventStoreDB and DynamoDB. Run them against a development database before production. github.com
The plugin route installs more than this skill
The backend-development plugin has 9 skills, 8 agents and 1 command. The repo tree shows no hooks or MCP config files in its folder. The skills-only routes install only this skill. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details

Turning on read-only	No read-only mode. Use version control.
Talks to	Connections to the database you point the templates at (the EventStoreDB example uses localhost:2113)
Scopes	Claude writes schema and application code in your project when you ask The templates create tables and indexes in PostgreSQL and connect to EventStoreDB or DynamoDB when you run them

Questions

What does the event-store-design skill do?

It gives Claude a guide to building event stores for event sourcing. Claude uses it to choose a technology and to write schemas and code for streams, versions, snapshots and subscriptions.

How do I install event-store-design?

Use the install box at the top of this page. It lists the plugin route and two skills-only commands: npx skills add wshobson/agents --skill event-store-design and gh skill install wshobson/agents event-store-design (GitHub CLI 2.90 or later). The skills-only commands skip the plugin's agents and commands.

Which store does it recommend?

It compares five and does not pick one. EventStoreDB is listed for pure event sourcing, PostgreSQL for an existing Postgres stack, Kafka for high-throughput streaming, DynamoDB for serverless AWS and Marten for .NET.

Which languages are the templates in?

SQL for the PostgreSQL schema and Python for the other three templates. The Marten option is only named in the comparison table.

Does it tell Claude to delete events?

No. The don'ts list says not to update or delete events because they are immutable facts.

Is it safe?

Installing it adds a guide and one reference file, with no scripts. The templates create tables and talk to a database when you run them, so try them on a development database first and review the SQL Claude generates.

Is this skill from Anthropic?

No. It is in wshobson/agents, a community collection. The skill sits in the backend-development plugin there.

Should I install the whole backend-development plugin?

Only if you want the rest. The README documents a plugin route for Claude Code and Codex. The plugin folder holds 9 skills, 8 agents and 1 command, and the repo tree shows no hooks or MCP config files in it.

Information

updated Nov 2, 2026

Repository: wshobson/agents
Folder: plugins/backend-development/skills/event-store-design

wshobson/agents skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 4

event-store-design SKILL.md · github.com
wshobson/agents README · github.com
backend-development plugin.json · github.com
event-store-design details.md · github.com