eda-event-designer

Name: eda-event-designer
Availability: InStock
Author: Medmo

Design EDA events with envelope, topic naming, partitioning, and schema registry rules.

Updated Mar 27, 2026

Search Tags:#documentation #kafka #eda #event-design #envelope #topic-naming

Ready to run

npx skills add https://github.com/medmo/conception-eda-wave --skill eda-event-designer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: eda-event-designer
Source: https://github.com/medmo/conception-eda-wave/tree/main/.claude/skills/eda-event-designer
Command: npx skills add https://github.com/medmo/conception-eda-wave --skill eda-event-designer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

Conçoit et documente un événement EDA complet en appliquant les bonnes pratiques du fichier eda_good_practice.md : enveloppe standard, nomenclature, nommage du topic Kafka, stratégie de partition, choix Événement de notification / Événement métier, patterns (Outbox, DLQ, idempotence), détection d'anti-patterns et checklist de validation.

Utilise ce skill dès que l'utilisateur demande : concevoir un événement EDA, définir un topic Kafka, valider la structure d'un événement, nommer un topic, choisir une partition key, appliquer les bonnes pratiques EDA, documenter un événement Kafka, vérifier qu'un design EDA est correct, ou générer un document de conception EDA.

Frequently Asked Questions about eda-event-designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I design a Kafka topic and event structure for EDA?▼

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.

What is the standard envelope for EDA event design?▼

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.

How do I validate a candidate Kafka topic name against EDA best practices?▼

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.

When should I use a notification event versus a business event in EDA?▼

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.

What EDA anti-patterns should I check before generating an event 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.

Does this EDA event design skill work without external dependencies?▼

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.