event-definition
Review or create event definitions for event-driven architecture. Covers event names, payload field names, event_type identity, stream naming boundaries, and record metadata/context/payload placement for both domain events (event-sourcing) and integration events (cross-service). Use when designing a new event definition, reviewing an existing event definition, or auditing event definition consistency across a catalog. Do not use for full event modeling workflows (use trogonstack-eventmodeling skills), event schema evolution or migration strategy, or event store implementation design.
Pinned to revision 67ecb834da20, so it is the text this page describes rather than whatever the author pushed since.
Pre-approved tools experimental
Experimental field. Support varies between clients, so this list is what the author declared, not what your client will enforce.
- AskUserQuestion
- Write
- Read
- Bash
Files
- skills/event-definition/SKILL.md
- skills/event-definition/references/event-naming-rules.md
- skills/event-definition/references/event-record-boundaries.md
- skills/event-definition/references/field-naming-rules.md
- skills/event-definition/references/quality-checklist.md
Every link opens the file at its source, pinned to the revision this page describes.