chatto-event-sourcing
Use when designing, implementing, reviewing, debugging, or documenting Chatto event-sourced domain behavior, including EVT subjects, aggregate boundaries, Services, projections, optimistic concurrency control, read-your-writes, live/reconnect delivery, replay compatibility, migration safety, and rollback/deployment implications.
67
Quality
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/chatto/chatto-event-sourcing/SKILL.mdCore Rules
- Durable domain facts go into
EVT. - Avoid adding new events to be stored in
EVTunless they are required to record a durable domain fact. - Multi-replica safety comes from JetStream OCC plus projection catch-up, not from in-process mutexes or "only one server will do this" assumptions.
- Every successful write that needs read-your-writes must wait for the local projector(s) that serve the next read path.
- Event subjects are part of the persisted data model. Changing an aggregate lane is a compatibility decision, not a refactor.
- Repository
- chattocorp/chatto
- Commit
5cbd584
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.