Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
wshobson avatar

Event Store Design

  • 8.5k installs
  • 38.3k repo stars
  • Updated July 22, 2026
  • wshobson/agents

event-store-design is an agent skill that Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing.

About

Design and implement event stores for event-sourced systems Use when building event sourcing infrastructure choosing event store technologies or implementing event persistence patterns name event-store-design description Design and implement event stores for event-sourced systems Use when building event sourcing infrastructure choosing event store technologies or implementing event persistence patterns Event Store Design Comprehensive guide to designing event stores for event-sourced applications When to Use This Skill Designing event sourcing infrastructure Choosing between event store technologies Implementing custom event stores Optimizing event storage and retrieval Setting up event store schemas Planning for event store scaling Core Concepts 1 Event Store Architecture Event Store Stream 1 Stream 2 Stream 3 Aggregate Aggregate Aggregate Event 1 Event 1 Event 1 Event 2 Event 2 Event 2 Event 3 Event 4 Global Position 1 2 3 4 5 6 2 Event Store Requirements Requirement Description Append-only Events are immutable only appends Ordered Per-stream and global ordering Versioned Optimistic concurrency control Subscriptions Real-time event notifications Idempotent Handle duplicate write.

  • Designing event sourcing infrastructure
  • Choosing between event store technologies
  • Implementing custom event stores
  • Optimizing event storage and retrieval
  • Setting up event store schemas

Event Store Design by the numbers

  • 8,460 all-time installs (skills.sh)
  • +159 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #111 of 4,386 Backend & APIs skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

event-store-design capabilities & compatibility

Capabilities
designing event sourcing infrastructure · choosing between event store technologies · implementing custom event stores · optimizing event storage and retrieval · setting up event store schemas
Use cases
documentation
From the docs

What event-store-design says it does

--- name: event-store-design description: Design and implement event stores for event-sourced systems.
SKILL.md
Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
SKILL.md
--- # Event Store Design Comprehensive guide to designing event stores for event-sourced applications.
SKILL.md
│ │ │ │ Event 4 │ │ │ └─────────────┘ └─────────────┘ └─────────────┘ │ ├─────────────────────────────────────────────────────┤ │ Global Position: 1 → 2 → 3 → 4 → 5 → 6 → ...
SKILL.md
npx skills add https://github.com/wshobson/agents --skill event-store-design

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs8.5k
repo stars38.3k
Security audit3 / 3 scanners passed
Last updatedJuly 22, 2026
Repositorywshobson/agents

What problem does event-store-design solve for developers using this skill?

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

Who is it for?

Developers who need event-store-design patterns described in the cached skill documentation.

Skip if: Skip when docs are empty or the task is outside the skill's documented scope.

When should I use this skill?

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

What you get

Actionable workflows and conventions from SKILL.md for event-store-design.

  • PostgreSQL events table schema
  • Python event store implementation

Files

SKILL.mdMarkdownGitHub ↗

Event Store Design

Comprehensive guide to designing event stores for event-sourced applications.

When to Use This Skill

  • Designing event sourcing infrastructure
  • Choosing between event store technologies
  • Implementing custom event stores
  • Optimizing event storage and retrieval
  • Setting up event store schemas
  • Planning for event store scaling

Core Concepts

1. Event Store Architecture

┌─────────────────────────────────────────────────────┐
│                    Event Store                       │
├─────────────────────────────────────────────────────┤
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐ │
│  │   Stream 1   │  │   Stream 2   │  │   Stream 3   │ │
│  │ (Aggregate)  │  │ (Aggregate)  │  │ (Aggregate)  │ │
│  ├─────────────┤  ├─────────────┤  ├─────────────┤ │
│  │ Event 1     │  │ Event 1     │  │ Event 1     │ │
│  │ Event 2     │  │ Event 2     │  │ Event 2     │ │
│  │ Event 3     │  │ ...         │  │ Event 3     │ │
│  │ ...         │  │             │  │ Event 4     │ │
│  └─────────────┘  └─────────────┘  └─────────────┘ │
├─────────────────────────────────────────────────────┤
│  Global Position: 1 → 2 → 3 → 4 → 5 → 6 → ...     │
└─────────────────────────────────────────────────────┘

2. Event Store Requirements

RequirementDescription
Append-onlyEvents are immutable, only appends
OrderedPer-stream and global ordering
VersionedOptimistic concurrency control
SubscriptionsReal-time event notifications
IdempotentHandle duplicate writes safely

Technology Comparison

TechnologyBest ForLimitations
EventStoreDBPure event sourcingSingle-purpose
PostgreSQLExisting Postgres stackManual implementation
KafkaHigh-throughput streamingNot ideal for per-stream queries
DynamoDBServerless, AWS-nativeQuery limitations
Marten.NET ecosystems.NET specific

Templates and detailed worked examples

Full template library and detailed worked examples live in references/details.md. Read that file when you need the concrete templates.

Best Practices

Do's

  • Use stream IDs that include aggregate type - Order-{uuid}
  • Include correlation/causation IDs - For tracing
  • Version events from day one - Plan for schema evolution
  • Implement idempotency - Use event IDs for deduplication
  • Index appropriately - For your query patterns

Don'ts

  • Don't update or delete events - They're immutable facts
  • Don't store large payloads - Keep events small
  • Don't skip optimistic concurrency - Prevents data corruption
  • Don't ignore backpressure - Handle slow consumers

Related skills

How it compares

Pick event-store-design over generic database design skills when you need opinionated PostgreSQL event store DDL and Python patterns for event sourcing.

FAQ

What does event-store-design do?

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

When should I use event-store-design?

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

Is event-store-design safe to install?

Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.