What problem does it solve? Writing MassTransit consumers for RabbitMQ integration events involves repetitive boilerplate — dependency injection, unit-of-work patterns, transaction handling, and retry semantics. This Skill scaffolds a complete, convention-compliant consumer class so developers avoid copy-paste errors and inconsistent patterns across services. ## Core Features & Use Cases - Two Consumer Templates: Generates either a DB-write-plus-notification consumer or a cross-service entity update consumer with explicit transaction handling. - Convention Enforcement: Places files in Infrastructure/Consumers/, wires assembly scanning for automatic discovery, and documents rules like not awaiting the void UpdateAsync() method. - Retry-Safe Error Handling: Templates throw on failure so MassTransit automatically retries, with rollback logic for transactional updates. - Use Case: When a BatteryAnomalyDetectedEvent must create a ticket in TicketService, run the scaffold to produce a ready-to-adapt BatteryAnomalyDetectedEventConsumer with logging, unit-of-work persistence, and DI registration guidance. ## Quick Start Ask the AI to scaffold a MassTransit consumer by providing the service name and event name, for example scaffold a consumer for TicketService handling BatteryAnomalyDetectedEvent.
