event
Skill4 starsChanged 2 months agoMITView on GitHub
Create a domain or integration event. Use when something significant happens that other parts of the system need to know about. Use this skill for domain events (same context, InternalMediator) and integration events (cross-context, ExternalMediator). Dispatch hub — routes to typescript/go variants by file extension.
Files
Event
A past-tense fact. Domain events stay inside one bounded context and trigger same-context handlers. Integration events cross context or service boundaries and are published via the outbox. Both carry a typed payload.
The shape and idioms of this primitive differ per backend language; the lang-specific playbooks below carry the concrete rules, code, and bad practices.
Ativação — qual mecanismo (decisão do founder, 29-jul-2026)
| Precisa de… | Mecanismo | Garantia | Quem entrega |
| "isto aconteceu, quem quiser reage" (fato, auditoria, event sourcing) | outbox — domain event no contexto; integration event pelo publisher nomeado | durável, at-least-once, fan-out | dispatcher/poller do outbox |
| "isto precisa acontecer, com retry, e alguém é o único executor" | CommandQueue — enqueueCommand(nome, input, opts, tx) na transação do fato | durável, retry+backoff, lease, dead-letter | o worker que registrou o comando |
| "turnos serializados por target" | Mailbox — produtores só ENFILEIRAM, sempre na transação do fato | durável, um turno por target de cada vez | o MailboxDispatcher (consumidor único) |
| "síncrono, nesta request" | use case chamado direto | a transação da própria request | o chamador |
A regra de intenção: evento existe para fins reativos, auditoria ou event sourcing — nunca para
comandar. Se a existência do evento é só para um handler executar algo que poderia ser um
comando/use case direto, está errado. Nomes *Requested não são proibidos por si; a intenção é o
critério. Enforcement: cc-bp-26 (cross-cutting, warning), handler bp-09 / bp-GO-HDL-07,
EVT-C11 / EVT-GO-09, UC-P16.
Language variants
| Backend | Playbook | Registry |
TypeScript — packages/api/typescript/ | typescript/SKILL.md | typescript/registry.yaml |
Go — packages/api/go/ | go/SKILL.md | go/registry.yaml |
How dispatch works
scripts/review.ts infers the language from the file extension (.ts / .go) and loads the matching <lang>/registry.yaml. The CLI scaffolder takes a --lang flag (--lang=typescript / --lang=go) or infers it from cwd. When editing or reviewing code, open the lang playbook matching the file you're touching — patterns and bad practices are coded per-language (e.g. EVT-GO-01).
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- GoogleCloudPlatform/opentelemetry-operations-collector★ 84same name
- proophboard/skills★ 6same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository45 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agentSkill
- bounded-contextSkill
- clean-branchSkill
- commitSkill
- componentSkill
- controllerSkill
- db-modellingSkill
- ddd-modelingSkill
- ddd-specSkill
- design-systemSkill
- desktop-shellSkill
- e2eSkill
- entitySkill
- enumSkill
- errorsSkill
- formSkill
- grill-with-docsSkill
- handlerSkill
- handoffSkill
- middlewareSkill
- migrateSkill
- prdSkill
- primitiveSkill
- projectionSkill
- projectorSkill
- querySkill
- repositorySkill
- reviewSkill
- routeSkill
- saas-researchSkill
- schedulerSkill
- schemaSkill
- sdkSkill
- serviceSkill
- spec-reviewSkill
- storeSkill
- storybookSkill
- task-breakdownSkill
- testSkill
- trace-analysisSkill
- ui-compositionSkill
- usecaseSkill
- user-storiesSkill
- value-objectSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.