What problem does it solve? Backend developers working on this .NET 9 microservices platform need a consistent, convention-driven way to create RabbitMQ consumers and integration events without guessing folder structure, naming patterns, or publish/commit ordering. ## Core Features & Use Cases - Integration Event Scaffolding: Defines events as C# records in SharedContracts/Events following the {Action}Event naming convention. - Consumer Implementation: Generates IConsumer<T> classes in Infrastructure/Consumers with UnitOfWork transaction handling and MassTransit auto-retry on throw. - Publish Ordering Rules: Enforces correct publish timing — after CommitTransactionAsync for services without Outbox, before SaveChangesAsync for services with Outbox. - Use Case: When adding a BatteryAnomalyDetectedEvent flow, the Skill produces the event record, the consumer with transactional business logic, and the AddMessageBus DI registration in one pass. ## Quick Start Ask the AI to create a MassTransit consumer and integration event for a new domain event, specifying which service publishes and which consumes.