Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dicklesworthstone/event-store-design
Design and implement event stores for event-sourced systems.
Passed 17 of 24 test cases with the skill, and 11 of 24 without it.
and 4 more in the full report
7 fixed10 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are designing event stream naming conventions for our financial microservices system. Provide recommendations on how to format stream IDs for aggregate instances such as orders, customer accounts, and payments to ensure consistency across the event store.
| Checked | Without skill | With skill |
|---|---|---|
| Formats aggregate stream identifiers using the pattern AggregateType-UUID. | 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 11 / 24 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.