Agent skill · software engineering · aiskillstore
blueprinteventbus-integration
Implement event-driven communication using BlueprintEventBus for cross-module coordination. Use this skill when modules need to communicate without tight coupling, broadcasting domain events (task.created, member.added), subscribing to events with proper lifecycle management, and implementing event-driven workflows. Ensures events follow naming conventions ([module].[action]), include Blueprint context, and use takeUntilDestroyed() for automatic cleanup.
Why this skill is useful
Provides specific implementation patterns and TypeScript interfaces for event-driven architecture using BlueprintEventBus that the AI wouldn't reliably generate on its own.
What it needs
About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
BlueprintEventBus Integration Skill This skill helps implement event-driven architecture using BlueprintEventBus. Core Principles Event-Driven Architecture Decoupling: Modules communicate via events, not direct calls Blueprint Context: All events include Blueprint information Type Safety: Events are strongly typed with TypeScript Lifecycle Management: Automatic subscription cleanup When to Use EventBus ✅ DO use EventBus for: Cross-module communication Broadcasting state changes to multiple listeners Audit logging and activity tracking Notification triggers Workflow orchestration ❌ DON'T use EventBus for: Simple parent-child component communication (use @Output) Direct service-to-service calls within same module Synchronous data fetching Request-response patterns (use Services) Event Structure Base Event Interface Event Naming Convention Examples: task.created task.updated task.deleted task.assigned member.added member.removed file.uploaded blueprint.archived Publishing Events Basic Event Publishing Typed Event Publishing Subscribing to Events Basic Subscription Filtered Subscription (Blueprint-specific) Multiple Event Types Common Use Cases 1. Audit Logging 2. Notification System 3. Real-time UI Updates 4. Workflow Orchestration Event Bus Service Implementation Reference implementation: Testing EventBus Integration Checklist When integrating EventBus: [ ] Events follow naming convention ([module].[action]) [ ] Events include blueprintId [ ] Events include timestamp and actor [ ] Subscriptions use takeUntilDestroyed() [ ] Filter events by Blueprint when needed [ ] Use typed events for type safety [ ] Publish events AFTER successful operations [ ] Don't use EventBus for request-response [ ] Test event publishing and subscription [ ] Document event types and data structures References Architecture Guide-architecture.instructions.md) Blueprint Integration Global Event Bus Documentation
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/blueprinteventbus-integration