create-entity

Estrellas13

Forks1

Actualizado10 de febrero de 2026 a las 01:24

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

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

jovicon

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

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

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

Create a new domain entity "$1" in the $0 module.

Create file: src/modules/$0/domain/$1.ts

Is this an aggregate root? $2 (default: yes)

Requirements:

If aggregate root (default):

Extend AggregateRoot from '@shared/ddd/AggregateRoot'
Include domain event publishing capability
Control transaction boundaries

If regular entity:

Extend Entity from '@shared/ddd/Entity'

Common requirements for both:

Use private constructor with static create() factory method
Include props interface for entity properties
Use UniqueEntityID for identity
Implement business logic methods (not just getters/setters)
Use Guard pattern for validation in the create() method
Return Result from create() method
Pure business logic - NO framework dependencies

Follow DDD principles:

Encapsulate business rules
Protect invariants
Use domain language
Keep logic in the domain layer

Reference the Order aggregate as an example.

Más de este repositorio

mismo repositorio

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-domain-event

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

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

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-entity
description	Create a new domain entity or aggregate root following DDD patterns. Use when modeling business entities with identity and lifecycle.

Create a new domain entity "$1" in the $0 module.

Create file: src/modules/$0/domain/$1.ts

Is this an aggregate root? $2 (default: yes)

Requirements:

If aggregate root (default):

Extend AggregateRoot from '@shared/ddd/AggregateRoot'
Include domain event publishing capability
Control transaction boundaries

If regular entity:

Extend Entity from '@shared/ddd/Entity'

Common requirements for both:

Use private constructor with static create() factory method
Include props interface for entity properties
Use UniqueEntityID for identity
Implement business logic methods (not just getters/setters)
Use Guard pattern for validation in the create() method
Return Result from create() method
Pure business logic - NO framework dependencies

Follow DDD principles:

Encapsulate business rules
Protect invariants
Use domain language
Keep logic in the domain layer

Reference the Order aggregate as an example.