event-catalogue

To document cross-service event schemas, you need a centralized, versioned event catalogue that governs contracts. This Skill generates a structured registry by reflecting over your event data implementations, enabling discovery and governance for event-driven architectures.

To prevent drift between event contracts and code, use build-time validation against your event catalogue. This Skill enforces sealed records and validates generated catalogue structures against your service assemblies to ensure documentation stays synchronized with code.

The best way to maintain a centralized event registry is to automate generation at build time. This Skill outputs a structured event catalogue by reflecting over IEventData implementations, enforcing consistent naming and versioning across producing and consuming services.

Yes, sealed records are required to generate an event catalogue using this Skill. The build-time generator enforces sealed records for your IEventData implementations to ensure strict immutability and reliable schema extraction for cross-service validation.

Yes, you can validate event versioning across different services automatically. This Skill enforces consistent naming and versioning of events within the generated catalogue, enabling cross-service contract validation to prevent incompatible schema deployments.

You need a versioned event catalogue when multiple services produce and consume events and teams require a discoverable contract. It solves the problem of scattered, inconsistent event schemas by providing centralized governance for cross-service communication.