What problem does it solve? Manually creating integration event contracts for async messaging is repetitive and error-prone: developers must remember the correct base class, file location, naming conventions, and publish-after-commit ordering. This Skill scaffolds a consistent IntegrationEvent record in the shared contracts project so cross-service events follow one standard. ## Core Features & Use Cases - Event Record Scaffolding: Generates a C# record extending the IntegrationEvent base class with Id and OccurredAt auto-set, placed in shared/SharedContracts/EventModels/. - Publisher Documentation: Embeds XML comments documenting which service publishes the event and which consumes it, keeping contracts self-describing. - Publishing Pattern Guidance: Shows the correct publish-after-CommitTransactionAsync pattern via _messageProducer.PublishAsync for services without an Outbox. - Use Case: When a battery anomaly is detected in BatteryService and TicketService must react, run the scaffold to create BatteryAnomalyDetectedEvent, then follow up with the consumer scaffold command. ## Quick Start Ask the AI to scaffold an integration event named BatteryAnomalyDetectedEvent for RabbitMQ messaging between services.