How do I install the Chatto Event Sourcing skill?

Run npx skillmds@latest add chattocorp/chatto-event-sourcing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Chatto Event Sourcing safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Chatto Event Sourcing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Chatto Event Sourcing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Chatto Event Sourcing?

chattocorp (@chattocorp) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Chatto Event Sourcing

Name: Chatto Event Sourcing
Author: chattocorp

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.

chattocorp Updated Sep 17, 2026

Coding & Dev Tools

Install

Press C to copy

$ npx skillmds@latest add chattocorp/chatto-event-sourcing

Installs into ~/.claude/skills (or .claude/skills inside a project). Restart Claude Code to pick it up.

Download SKILL.md

＋ Add to collection

README badge

[![SkillMD](https://skillmd.com/badge/chattocorp/chatto-event-sourcing.svg)](https://skillmd.com/skills/chattocorp/chatto-event-sourcing)

Trust & safety

Audits pending

Not yet audited · commit 75d3252

Works with: Claude Code Claude.ai OpenAI Codex +

File contents

Core Rules

Durable domain facts go into EVT.
Avoid adding new events to be stored in EVT unless 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.

chattocorp/chatto/tree/main/.agents/skills/chatto/chatto-event-sourcing commit 75d3252627

Frequently asked questions

npx skillmds@latest add chattocorp/chatto-event-sourcing