Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →wshobson/event-store-design
Design and implement event stores for event-sourced systems.
Passed 20 of 22 test cases with the skill, and 18 of 22 without it.
and 1 more in the full report
3 fixed17 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to add a required field to a `CustomerRegistered` event payload, but existing consumers still expect the original schema shape. What event evolution strategy maintains backward compatibility?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends using upcasters to convert historical event payloads to the target schema version | Missed | Passed |
The instructions your model reads when the skill loads.
Comprehensive guide to designing event stores for event-sourced applications.
┌─────────────────────────────────────────────────────┐
│ 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 → ... │
└─────────────────────────────────────────────────────┘
| Requirement | Description |
|---|---|
| Append-only | Events are immutable, only appends |
test cases passed, vs 18 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.