Create domain and integration events with transactional outbox delivery in TypeScript and Go backends.
npx skills add https://github.com/gabriellst/codm --skill event-gabriellst
Please help me install this Agent Skill. Skill: event Source: https://github.com/gabriellst/codm/tree/main/.claude/skills/event Command: npx skills add https://github.com/gabriellst/codm --skill event-gabriellst
TranscodingJobStartedEvent in Go (type alias over types.DomainEvent[T], past-tense const name, primitive payload with JSON tags), raise it inside the entity method, and let the repository drain it to the outbox. ## Quick Start Ask the agent to create a domain event for a significant occurrence in your bounded context, for example: create an event for when a collaborator is invited in the collaborator context.High-intent search queries and answers about installing and using this skill.
Define a payload schema with z.domainEvent(), create a class extending BaseDomainEvent with a static past-tense name like 'collaborator.collaborator.invited', and save it via domainEventRepository.save inside the same transaction as the entity. The OutboxDispatcher delivers it asynchronously.
Domain events stay within one bounded context and are delivered via the outbox to InternalMediator handlers. Integration events cross context or service boundaries, live in a shared events module, and are published by a named handler through ExternalMediator.
Direct publishing loses durability: if the process crashes after the database commit but before dispatch, the event is lost. Saving the event to the outbox in the same transaction guarantees at-least-once delivery by the polling dispatcher.
Declare a payload struct with plain primitives and JSON tags, then create a type alias like type MyEvent = types.DomainEvent[MyPayload] so it satisfies DomainEventI automatically. Add a NewMyEvent constructor taking entityID, ownerID, and payload.
Use a command queue when something must happen with retry and a single executor, rather than when a fact occurred that others may react to. Events exist for reactive, audit, or event-sourcing purposes — never to command an action.
Payloads must use plain serializable primitives such as strings, numbers, booleans, dates, and enum references. Entity pointers, live class instances, value objects, and non-serializable runtime objects like HTTP requests are prohibited because they break outbox serialization.
Jin9Define bounded contexts, aggregates, and domain events using DDD building blocks.
tthanhtung9922Create domain event records and mediator-based handlers for cache invalidation and side effects.
hiiamskyPersist domain events atomically with aggregates using EF Core, Quartz, and MediatR.
zhou210712Draft litigation document sections with citation and verification tags.