skills.rest
hassanhabib
hassanhabibCOMMUNITY
Explore all skills by this author →
Website𝕏@HassanRezkHabibGitHub

The Standard Events

Standardize cross-service event-driven communication with publish-subscribe workflows and IEventBroker patterns.

18|6|Updated Mar 25, 2026
Search Tags:#testing#architecture#startup#event-driven#di#broker#levent
One-click install
npx skills add https://github.com/hassanhabib/the-standard-skills --skill the-standard-events
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: The Standard Events
Source: https://github.com/hassanhabib/the-standard-skills/tree/main/.skills/the-standard-events
Command: npx skills add https://github.com/hassanhabib/the-standard-skills --skill the-standard-events

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Standard Events standardizes how services publish and subscribe to domain events, enforcing a deterministic CulDeSac pattern, foundation event services, and consistent testing to reduce integration risk.

Core Features & Use Cases

  • Standardizes event broker structure using LeVent, per-entity event clients, and thin broker passes through.
  • Enforces two operations per entity: Publish[Entity]Async and SubscribeTo[Entity]Event, with validated inputs and structured exception handling.
  • Supports startup activation for orchestration subscriptions and DI wiring across bounded contexts.

Quick Start

Register the event broker and event services in DI, then activate subscriptions at startup using the prescribed startup pattern.

Frequently Asked Questions about The Standard Events

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

FAQPage Schema
How do I standardize event-driven communication across bounded contexts?▼

Event-driven communication across bounded contexts is standardized using a deterministic broker interface, per-entity publish and subscribe operations, and DI startup activation. This enforces consistent cross-service workflows and reduces integration risk.

What is the best way to structure a publish-subscribe workflow for domain events?▼

A publish-subscribe workflow is structured using an IEventBroker interface with thin passes through to per-entity event clients. Each entity requires two operations: Publish[Entity]Async and SubscribeTo[Entity]Event, ensuring validated inputs and structured exception handling.

How do I register and activate event subscriptions at startup?▼

Event subscriptions are registered by wiring the event broker and event services into dependency injection, then activating orchestration subscriptions at startup using the prescribed startup pattern to ensure reliable event-driven execution.

Does the event broker pattern support validation and exception handling for domain events?▼

The event broker pattern supports validation and exception handling by requiring validated inputs and structured exception mapping for all per-entity publish and subscribe operations. This ensures deterministic CulDeSac processing and reduces integration failures.

Why does my cross-service event orchestration fail without a standardized broker interface?▼

Cross-service event orchestration fails without a standardized broker interface because inconsistent publish-subscribe workflows lack validated inputs and structured exception mapping. Enforcing a deterministic pattern with per-entity operations and DI startup activation eliminates these integration risks.

Related Skills

Explore More Software Engineering Skills→
recca0120recca0120
11

inversify-di

Standardize Inversify DI bindings with a shared TYPES symbol registry.

Community
Intermediate
michsindlingermichsindlinger
1

Backend Logic Implementer

Implement backend business logic with clean architecture and SOLID principles.

Community
Advanced
hassanhabibhassanhabib
18

The Standard Testing

Enforce three-axis test structure and exception-mapping rules for The Standard-compliant systems.

Community
Advanced
FlexNetOSFlexNetOS

Messaging & Event Systems

Coordinate NATS pub/sub and Temporal workflows for distributed messaging.

Community
Advanced