eda-event-designer

Designing an EDA event requires defining a standard envelope, applying Kafka topic naming conventions, and selecting a partition key. This skill generates the full event design and documentation by enforcing schema registry strategy and validating against EDA anti-patterns.

The standard EDA event envelope structures event metadata and payload for Kafka transmission. This skill enforces the envelope structure during event conception and identification to generate validated design artifacts and consistent documentation.

Validating a candidate Kafka topic name involves checking it against EDA naming conventions, partition rules, and anti-patterns. This skill operates in identification mode to validate candidate event names from domain context and confirm topic naming correctness.

Choosing between notification and business events depends on payload size and consumer autonomy. This skill applies EDA patterns to guide this choice during event conception, enforcing the correct schema registry strategy and producing a validated design document.

EDA anti-pattern checks include validating idempotence, Outbox pattern usage, and DLQ strategy. This skill detects anti-patterns during event conception and applies a validation checklist before generating the final EDA design document.

Yes, this EDA event design skill operates without external dependencies, relying solely on internal assets to apply EDA patterns and topic naming rules. It generates design artifacts and documentation directly from the provided domain context.