What problem does it solve? Event-driven architectures need consistent, idempotent handlers that react to domain and integration events without duplicating side effects on retries. This Skill scaffolds and reviews event handlers across a polyglot backend (TypeScript daemon and Go gateway), enforcing the correct mediator registration, outbox patterns, and error-handling rules per language. ## Core Features & Use Cases - Dual-language dispatch: Routes to TypeScript or Go playbooks based on file extension, with per-language registries of mandatory patterns and bad practices. - Internal and external handlers: Covers same-context domain event handlers, cross-context integration event consumers, and named integration-event publishers via ExternalMediator. - Idempotency and error policy: Enforces existence checks or entity-level deduplication, outbox-based event chaining, and critical vs non-critical error handling rules. - Use Case: When a WhatsApp message arrives and a MessageReceived domain event fires, scaffold a handler that republishes it as an integration event, then a second handler in another context that reacts by creating a collaborator record idempotently. ## Quick Start Ask the agent to create an event handler for a specific domain event in a given context, for example: create a handler that sends a welcome email when the UserCreated event fires in the auth context.