メニュー
Creates a domain event handler that reacts to events from another module (or the same module). Includes handler class and unit test. Use after domain events have been created with /api-add-domain-entity.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | api-add-event-handler |
| description | Creates a domain event handler that reacts to events from another module (or the same module). Includes handler class and unit test. Use after domain events have been created with /api-add-domain-entity. |
Creates a domain event handler in the application layer. Event handlers react to domain events published by repositories after DB writes.
Read the ## Configuration section in .claude/CLAUDE.md for {SHARED_ROOT} and {MODULE_ROOT}.
Run these skills first (in order):
/api-init-project — project scaffold/api-setup-shared — shared base classes (DomainEvent, IDateProvider, etc.)/api-add-module — module scaffold (application module with CqrsModule)/api-add-domain-entity (with AggregateRoot) — creates the domain events this handler reacts toCreate handler — application/event-handlers/{action}-when-{event}.event-handler.ts
Load references/event-handler-template.md.
{Action}When{Event}Handler (e.g., CreateWalletWhenUserCreatedHandler)@EventsHandler(XxxEvent)IEventHandler<XxxEvent> with handle(event) method@Inject(TOKEN) — same pattern as command handlersCreate unit test — application/event-handlers/{action}-when-{event}.event-handler.spec.ts
Load references/test-template.md.
handler.handle(event)Register handler — add the handler class to application/{module-name}.module.ts providers array.
List the handler directly — no barrel file.
/api-add-domain-entity.Adds a new domain error to an existing module — extends the module base error, sets error code and monitoring flag, and updates the exception filter mapping. Use when a command or query needs to throw a new business error. Requires /api-add-module.
Adds a new HTTP endpoint to an existing controller — request/response DTOs, Swagger decorators, and command/query wiring. Use after the module, entity, and command/query already exist. Requires /api-setup-shared and /api-add-module.
Creates a CQRS command + handler + in-memory test in a NestJS hexagonal module. Use when adding a write operation (state change) to a module. Command and handler live in the same file. Requires /api-setup-shared.
Creates a complete domain entity in a NestJS hexagonal module — entity, repository interface, test builder, unit tests, SQL repository, in-memory repository, mapper, and optionally domain events. Supports both standalone entities and AggregateRoot entities with domain event publishing. Use when adding a new aggregate to a module's domain layer.
Creates a CQRS query + handler + integration test in a NestJS hexagonal module. Use when adding a read operation (data retrieval) to a module. Query and handler live in the same file. Handlers bypass the domain and repository layers entirely — direct PrismaService only. Requires /api-setup-shared.
Creates all shared infrastructure required for hexagonal NestJS modules — TypedCommand, TypedQuery, TypedCommandBus, TypedQueryBus, CorrelationId decorator, PaginatedQueryBase, BaseDomainError, BaseFeatureExceptionFilter, the BaseLogger pattern (wrapping nestjs-pino), ZodValidationPipe with @ZodSchema decorator, PrismaService + PrismaModule (global), validateEnv helper, CqrsInterceptor (bus observer), LoggingInterceptor (HTTP request logger), DomainEvent base class, SqlRepositoryBase (generic Prisma CRUD + auto event publishing), and IDateProvider + DateProvider + FakeDateProvider (date abstraction for deterministic testing). Run once per project before using other api-* skills.