create-domain-event

Étoiles13

Forks1

Mis à jour10 février 2026 à 01:24

Create a domain event and its handler following DDD patterns. Use when you need to publish domain events for asynchronous reactions.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

jovicon

jovicon/nestjs-clean-architecture-event-driven-template

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	create-domain-event
description	Create a domain event and its handler following DDD patterns. Use when you need to publish domain events for asynchronous reactions.

Create a domain event "$1" and its handler in the $0 module.

Create these files:

src/modules/$0/domain/events/$1.ts
- Pure data event extending DomainEvent base class
- NO framework decorators (no @Injectable, @OnEvent)
- Only domain data
src/modules/$0/application/events/handlers/$1.handler.ts
- Event handler with framework support
- Use @Injectable() and @OnEvent() decorators
- Implement business logic that reacts to the event

Requirements:

Domain Event (domain layer): Pure TypeScript, extends DomainEvent from '@shared/ddd/DomainEvent.base'
Event Handler (application layer): NestJS decorators, implements IEventHandler
Follow the pattern: Domain emits data-only events, Application reacts with handlers
Reference the OrderCreated event and handler as examples

IMPORTANT: Respect layer boundaries:

Domain events = Pure data, no framework dependencies
Event handlers = Framework integration (@Injectable, @OnEvent)

Plus depuis ce dépôt

même dépôt

analyze-architecture

jovicon/nestjs-clean-architecture-event-driven-template

Analyze NestJS project architecture against Clean Architecture, DDD, and best practices. Use when reviewing code structure, checking layer boundaries, validating architectural patterns, or auditing module compliance.

2026-02-1013

analyze-code-quality

jovicon/nestjs-clean-architecture-event-driven-template

Analyze code quality including ESLint, Prettier, tests, TypeScript, and NestJS best practices. Use when reviewing code quality, checking test coverage, or auditing for best practices.

2026-02-1013

architecture-guide

jovicon/nestjs-clean-architecture-event-driven-template

Quick reference guide for architectural decisions and patterns in Clean Architecture + DDD + Event-Driven systems. Use for learning or when making architectural decisions.

2026-02-1013

create-entity

jovicon/nestjs-clean-architecture-event-driven-template

Create a new domain entity or aggregate root following DDD patterns. Use when modeling business entities with identity and lifecycle.

2026-02-1013

create-module

jovicon/nestjs-clean-architecture-event-driven-template

Create a new feature module following Clean Architecture structure. Use when adding a new business domain or feature module to the project.

2026-02-1013

create-repository

jovicon/nestjs-clean-architecture-event-driven-template

Create repository adapter with MongoDB schema following the ports & adapters pattern. Use when adding persistence for domain entities.

2026-02-1013

name	create-domain-event
description	Create a domain event and its handler following DDD patterns. Use when you need to publish domain events for asynchronous reactions.

Create a domain event "$1" and its handler in the $0 module.

Create these files:

src/modules/$0/domain/events/$1.ts
- Pure data event extending DomainEvent base class
- NO framework decorators (no @Injectable, @OnEvent)
- Only domain data
src/modules/$0/application/events/handlers/$1.handler.ts
- Event handler with framework support
- Use @Injectable() and @OnEvent() decorators
- Implement business logic that reacts to the event

Requirements:

Domain Event (domain layer): Pure TypeScript, extends DomainEvent from '@shared/ddd/DomainEvent.base'
Event Handler (application layer): NestJS decorators, implements IEventHandler
Follow the pattern: Domain emits data-only events, Application reacts with handlers
Reference the OrderCreated event and handler as examples

IMPORTANT: Respect layer boundaries:

Domain events = Pure data, no framework dependencies
Event handlers = Framework integration (@Injectable, @OnEvent)