From 4028ee64b7fe46e4f476812c51e0d60f42029e76 Mon Sep 17 00:00:00 2001 From: Yordis Prieto Date: Tue, 26 May 2026 02:25:50 -0400 Subject: [PATCH] fix(eda): avoid narrow event naming trigger Signed-off-by: Yordis Prieto --- .../.claude-plugin/plugin.json | 2 +- plugins/trogonstack-eda/README.md | 2 +- .../{event-name => event-definition}/SKILL.md | 31 +++++++++---------- .../references/event-naming-rules.md | 2 +- .../references/event-record-boundaries.md | 0 .../references/field-naming-rules.md | 2 +- .../references/quality-checklist.md | 0 7 files changed, 19 insertions(+), 20 deletions(-) rename plugins/trogonstack-eda/skills/{event-name => event-definition}/SKILL.md (84%) rename plugins/trogonstack-eda/skills/{event-name => event-definition}/references/event-naming-rules.md (97%) rename plugins/trogonstack-eda/skills/{event-name => event-definition}/references/event-record-boundaries.md (100%) rename plugins/trogonstack-eda/skills/{event-name => event-definition}/references/field-naming-rules.md (97%) rename plugins/trogonstack-eda/skills/{event-name => event-definition}/references/quality-checklist.md (100%) diff --git a/plugins/trogonstack-eda/.claude-plugin/plugin.json b/plugins/trogonstack-eda/.claude-plugin/plugin.json index 335fa6f..667e759 100644 --- a/plugins/trogonstack-eda/.claude-plugin/plugin.json +++ b/plugins/trogonstack-eda/.claude-plugin/plugin.json @@ -1,6 +1,6 @@ { "name": "trogonstack-eda", - "description": "Event-driven architecture skills for designing event names, schemas, contracts, and catalogs following good practices for domain and integration events", + "description": "Event-driven architecture skills for designing event definitions, schemas, contracts, and catalogs following good practices for domain and integration events", "version": "0.1.0", "author": { "name": "TrogonStack", diff --git a/plugins/trogonstack-eda/README.md b/plugins/trogonstack-eda/README.md index 782b849..bc0e5d6 100644 --- a/plugins/trogonstack-eda/README.md +++ b/plugins/trogonstack-eda/README.md @@ -1,6 +1,6 @@ # trogonstack-eda -Event-driven architecture skills for designing event names, schemas, contracts, and catalogs following good practices for domain and integration events. +Event-driven architecture skills for designing event definitions, schemas, contracts, and catalogs following good practices for domain and integration events. ```bash claude plugin install trogonstack-eda@trogonstack diff --git a/plugins/trogonstack-eda/skills/event-name/SKILL.md b/plugins/trogonstack-eda/skills/event-definition/SKILL.md similarity index 84% rename from plugins/trogonstack-eda/skills/event-name/SKILL.md rename to plugins/trogonstack-eda/skills/event-definition/SKILL.md index 8542944..190be16 100644 --- a/plugins/trogonstack-eda/skills/event-name/SKILL.md +++ b/plugins/trogonstack-eda/skills/event-definition/SKILL.md @@ -1,16 +1,15 @@ --- -name: event-name +name: event-definition description: >- - Review or create event names and payload field names following - event-driven architecture conventions. Covers both domain events - (event-sourcing) and integration events (cross-service). Validates - tense, specificity, field naming, and metadata placement. Use when - designing new events, reviewing existing event definitions, or - auditing naming consistency across an event catalog. Do not use for: - (1) event schema evolution or versioning strategy (use event-design-contract), - (2) full event payload design (use event-design-domain-schema or - event-design-integration-schema), (3) event modeling workflows - (use trogonstack-eventmodeling skills). + Review or create event definitions for event-driven architecture. + Covers event names, payload field names, event_type identity, stream + naming boundaries, and record metadata/context/payload placement for + both domain events (event-sourcing) and integration events (cross-service). + Use when designing a new event definition, reviewing an existing event + definition, or auditing event definition consistency across a catalog. + Do not use for full event modeling workflows (use trogonstack-eventmodeling + skills), event schema evolution or migration strategy, or event store + implementation design. allowed-tools: - AskUserQuestion - Write @@ -18,9 +17,9 @@ allowed-tools: - Bash --- -# Review or Create Event Names +# Review or Create Event Definitions -Review or create event names and payload field names for event-driven systems. Keep the default pass focused on naming, field placement, and the quality gate; load references only when a decision needs examples, detailed criteria, or deeper modeling guidance. +Review or create event definitions for event-driven systems. Keep the default pass focused on event identity, naming, field placement, record boundaries, and the quality gate; load references only when a decision needs examples, detailed criteria, or deeper modeling guidance. ## Progressive Disclosure @@ -33,7 +32,7 @@ Read these references only when the task needs that depth: ## Core Principle -An event name declares **what happened** as a fact. A payload field name declares **what business fact was captured** about that event. +An event definition declares **what happened**, **how it is identified**, and **which business facts were captured**. Keep three layers distinct: @@ -45,13 +44,13 @@ Do not push generic causality, tracing, persistence, or transport facts into the ## Interview -Before reviewing or creating names, establish: +Before reviewing or creating event definitions, establish: 1. **Domain or integration?** Domain events live inside a bounded context and are the source of truth for state. Integration events cross service boundaries and form a public contract. 2. **What business process or workflow does this event belong to?** 3. **What conventions already exist in the codebase?** If there is an event catalog, read it first and follow it unless it violates these rules. -If the user provides event names to review, skip to the review. If the user asks to design new events, gather the business context first. +If the user provides event definitions to review, skip to the review. If the user asks to design new event definitions, gather the business context first. ## Event Naming Rules diff --git a/plugins/trogonstack-eda/skills/event-name/references/event-naming-rules.md b/plugins/trogonstack-eda/skills/event-definition/references/event-naming-rules.md similarity index 97% rename from plugins/trogonstack-eda/skills/event-name/references/event-naming-rules.md rename to plugins/trogonstack-eda/skills/event-definition/references/event-naming-rules.md index b70fb82..e3309fb 100644 --- a/plugins/trogonstack-eda/skills/event-name/references/event-naming-rules.md +++ b/plugins/trogonstack-eda/skills/event-definition/references/event-naming-rules.md @@ -1,6 +1,6 @@ # Event Naming Rules -Use this reference when the default event-name skill needs examples or edge-case guidance for event names. +Use this reference when the default event-definition skill needs examples or edge-case guidance for event names. ## Past Tense diff --git a/plugins/trogonstack-eda/skills/event-name/references/event-record-boundaries.md b/plugins/trogonstack-eda/skills/event-definition/references/event-record-boundaries.md similarity index 100% rename from plugins/trogonstack-eda/skills/event-name/references/event-record-boundaries.md rename to plugins/trogonstack-eda/skills/event-definition/references/event-record-boundaries.md diff --git a/plugins/trogonstack-eda/skills/event-name/references/field-naming-rules.md b/plugins/trogonstack-eda/skills/event-definition/references/field-naming-rules.md similarity index 97% rename from plugins/trogonstack-eda/skills/event-name/references/field-naming-rules.md rename to plugins/trogonstack-eda/skills/event-definition/references/field-naming-rules.md index 8dcec05..588e830 100644 --- a/plugins/trogonstack-eda/skills/event-name/references/field-naming-rules.md +++ b/plugins/trogonstack-eda/skills/event-definition/references/field-naming-rules.md @@ -1,6 +1,6 @@ # Field Naming Rules -Use this reference when the default event-name skill needs examples or edge-case guidance for event payload fields. +Use this reference when the default event-definition skill needs examples or edge-case guidance for event payload fields. ## What, Who, When diff --git a/plugins/trogonstack-eda/skills/event-name/references/quality-checklist.md b/plugins/trogonstack-eda/skills/event-definition/references/quality-checklist.md similarity index 100% rename from plugins/trogonstack-eda/skills/event-name/references/quality-checklist.md rename to plugins/trogonstack-eda/skills/event-definition/references/quality-checklist.md