Emit and subscribe to typed domain events via a central event bus.
npx skills add https://github.com/aydadevelop/turborepo-starter --skill domain-events
Please help me install this Agent Skill. Skill: domain-events Source: https://github.com/aydadevelop/turborepo-starter/tree/main/.agents/skills/domain-events Command: npx skills add https://github.com/aydadevelop/turborepo-starter --skill domain-events
This Skill provides a robust and type-safe system for emitting and subscribing to domain-specific events within the application, decoupling services and enabling event-driven architecture.
clearEventPushers for isolated testing of event-driven logic.booking:created event is emitted, the notifications module can automatically subscribe and send an email to the customer, while the calendar module subscribes to booking:confirmed to update the booking's calendar entry.Register a new event pusher to handle the 'booking:confirmed' event.
High-intent search queries and answers about installing and using this skill.
An event bus enables pub/sub communication by allowing modules to register as listeners for typed domain events while domain services emit events with structured payloads, achieving decoupled event-driven architecture.
Decouple services by registering modules as event pushers on a central event bus, enabling domain services to emit typed events like 'booking:created' that other modules subscribe to without direct dependencies.
Yes, you can test event-driven logic in isolation by calling the clearEventPushers utility, which clears event subscriptions to ensure subscribers are not triggered during testing.
TypeScript event-driven architecture supports typed payloads for domain events, providing a type-safe system where domain services publish structured data that subscribers receive with full type checking.
The best way to structure event subscriptions is through a central event bus where modules register as listeners for specific event types, allowing domain services to emit structured events that automatically trigger the correct subscribers.
A central event bus for domain events should not be used when modules require synchronous, tightly coupled execution or when the testing overhead of managing and clearing event subscriptions outweighs the benefits of decoupling.
semicolon-devteamGenerate TypeScript event envelope types and Zod schemas from event contracts.
nextplus896Automates Laravel background processing with Jobs, Listeners, Actions, and ShouldQueue.
fgarofalo56Manage event routing and subscriptions for Azure Event Grid.
Camilo8902Design event-driven architectures with event sourcing, CQRS, and pub/sub patterns.