Skip to content
Get packs

Event Store Design

Guides the agent in designing event stores for event-sourced applications, including technology choices and persistence patterns.

Source Download skill
Repository
wshobson/agents
Stars
42,095
Licence
MIT
Files
2 files

What it does

Once installed, the agent answers event-sourcing architecture questions with a structured design approach: how to organise streams per aggregate, which ordering, versioning and idempotency rules to apply, and how to compare options such as EventStoreDB, PostgreSQL, Kafka, DynamoDB and Marten. It points to a reference file of templates and worked examples when concrete code or schemas are needed. It is a guidance document rather than a tool that builds or changes anything by itself.

Great for

  • Backend engineers planning an event-sourced system and choosing where to store events
  • Teams deciding between a dedicated event store and building one on an existing PostgreSQL stack
  • Developers who want a checklist of event store do's and don'ts such as append-only storage and optimistic concurrency

Skip it if

  • Projects that only need simple CRUD storage, since event sourcing adds significant complexity the guide does not weigh against its benefits
  • Non-developers looking for a finished product; the output is design advice that still needs engineering review and testing

Try asking

  • “Design an event store schema for an order management system using PostgreSQL”
  • “Compare EventStoreDB, Kafka and DynamoDB for a serverless event-sourced application”
  • “Review my stream ID and event versioning strategy for event sourcing”
  • “Show me a template for implementing idempotent event appends”
Step-by-step guide: how to use Event Store DesignInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 2 original files, the MIT licence and an attribution note.

    event-store-design.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip event-store-design.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip event-store-design.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Name the database or language you use (for example .NET or PostgreSQL) so the agent narrows the technology comparison to your stack
  • Ask for the reference templates explicitly if you want concrete code rather than high-level advice
  • Check generated schemas against your own scaling and retention needs, since the guide is brief on performance tradeoffs

What's inside

  • references/details.md
  • SKILL.md

Redistributed unmodified from wshobson/agents under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.