skills.rest
hiiamsky
hiiamskyCOMMUNITY
Explore all skills by this author →
GitHub

domain-events-generator

Generate domain event records and handler scaffolding with outbox wiring.

Updated Apr 4, 2026
Search Tags:#ddd#code-generation#event-sourcing#outbox#domain-events#mediatR
One-click install
npx skills add https://github.com/hiiamsky/multi-agent-dev-team --skill domain-events-generator-hiiamsky
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: domain-events-generator
Source: https://github.com/hiiamsky/multi-agent-dev-team/tree/main/.github/skills/dotnet-domain-events
Command: npx skills add https://github.com/hiiamsky/multi-agent-dev-team --skill domain-events-generator-hiiamsky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Domain-driven design often requires numerous boilerplate pieces for domain events, their records, and handlers. This skill automates the scaffolding of domain events and related handlers, ensuring consistent structure and interop with MediatR and the Outbox pattern.

Core Features & Use Cases

  • Template-driven generation of {Entity}CreatedDomainEvent, {Entity}UpdatedDomainEvent, and other domain events.
  • Outbox wiring templates to ensure reliable event delivery across Domain, Application, and Infrastructure layers.
  • Ready-made event handlers and templates to accelerate integration with MediatR and read-model updates.
  • Naming conventions and project structure guidance for scalable event-centric architectures.

Quick Start

Run the domain-events generator to scaffold domain events, handlers, and outbox wiring for your domain.

Frequently Asked Questions about domain-events-generator

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

FAQPage Schema
How do I scaffold domain events and handlers for a DDD project?▼

Scaffolding domain events is automated by generating event interfaces, records, and handler templates across Domain, Application, and Infrastructure layers. It enforces templated contracts and outbox wiring to support reliable event delivery.

What is the outbox pattern in event sourcing and when do I need it?▼

The outbox pattern ensures reliable event delivery by wiring domain events through a transactional outbox. You need it when building event-centric architectures to guarantee that state changes and event publications are committed atomically.

Can I use MediatR with domain events in a .NET DDD architecture?▼

Yes, MediatR integration is supported by generating ready-made event handlers and templates. It accelerates integration for dispatching domain events and updating read models within your Application layer.

What's the best way to generate boilerplate code for domain events?▼

Generating domain events boilerplate is best handled through template-driven automation. It creates consistent naming conventions and project structures for entities like {Entity}CreatedDomainEvent and {Entity}UpdatedDomainEvent.

Does domain event scaffolding enforce specific project structure conventions?▼

Yes, domain event scaffolding enforces project structure guidance and naming conventions for scalable event-centric architectures. It ensures consistent separation across Domain, Application, and Infrastructure layers.

Related Skills

Explore More Software Engineering Skills→
marcioaltoemarcioaltoe
14

code-standards

Enforce SOLID principles and Clean Code patterns across classes and modules.

Community
Advanced
ronnythedevronnythedev
69

domain-events-generator

Generate domain events, handlers, and Outbox integration using MediatR.

Community
Intermediate
haxlyshaxlys

cqrs-implementation

Separate command and query paths with event-sourced projections in FastAPI.

Community
Advanced
VictorHueniVictorHueni

arch-service-contract

Generate interface contracts for bounded contexts and product APIs.

Community
Advanced