Back to skills
SKILL.md
Api Event Rabbitmq
ASecurityGenerate RabbitMQ event publishers and subscribers with tenant routing, durable queues, and automatic reconnection. Use when implementing event-driven architecture or cross-service communication.
- 2 stars
- 0 votes
- 0 copies
- 0 views
- Added September 27, 2026
Works with
Security analysis
100/100npx -y skills add David-Li0406/meta-skill-evloving --skill api-event-rabbitmq --agent claude-codeAre you the author of Api Event Rabbitmq?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/david-li0406-api-event-rabbitmq)---
name: api-event-rabbitmq
description: Generate RabbitMQ event publishers and subscribers with tenant routing, durable queues, and automatic reconnection. Use when implementing event-driven architecture or cross-service communication.
allowed-tools:
- Read
- Write
- Edit
- Glob
- Grep
---
# RabbitMQ Event Bus
## Purpose
Generate RabbitMQ event bus services for publishing and subscribing to domain events with tenant routing, durable queues, and automatic reconnection.
## When to Use
- Implementing event-driven architecture
- Cross-service communication
- Async event processing
- Domain event sourcing
- Microservices integration
## What It Generates
### Directory Structure
```
apps/api/src/modules/{feature}/events/
├── publishers/
│ ├── {event}.publisher.ts
│ └── index.ts
├── subscribers/
│ ├── {event}.subscriber.ts
│ └── index.ts
└── index.ts
```
## Patterns Enforced
### Tenant Routing
Events use tenant-specific routing keys:
- Format: `{tenantId}.{event.pattern}`
- Enables tenant-scoped event handling
- Supports wildcard subscriptions
### Durable Queues
Queues survive broker restarts:
- `queueOptions: { durable: true }`
- Messages persisted
- No data loss on restart
### Persistent Messages
Messages survive broker restart:
- `messageOptions: { persistent: true }`
- Critical for domain events
- At-least-once delivery
### Acknowledgments
Manual ack for reliability:
- Handlers ack on success
- Handlers nack on failure
- Dead letter for failed events
## Usage Example
```bash
/skill event-rabbitmq --name=User --events='created,updated,deleted'
```
## Related Files
- [Feature CQRS](../../core/feature-cqrs/SKILL.md) - Events in CQRS handlers
- [BullMQ Queues](../queue-bullmq/SKILL.md) - Queue jobs from events
Attribution
Comments
Loading comments…