nestjs-hexagonal

Creates application layer artifacts for a NestJS bounded context — use cases, CQRS command/query handlers, DTOs, ports, and application services. Dispatched by create-subdomain workflow or triggered by "create use case", "add handler", "cqrs command".

Reviews a bounded context for Hexagonal Architecture + DDD + CQRS compliance. Specializes in detecting over-engineering and code smells. Produces structured reports with architecture compliance, over-engineering audit, and code smell detection. Use after implementing a bounded context, when asked to "review architecture", "check for over-engineering", or "review bounded context".

Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.

Creates domain layer artifacts for a NestJS bounded context — entities (AggregateRoot), value objects, domain events, repository interfaces, domain services, validators, and data builders. Uses Opus 4.6 for critical domain modeling decisions. Dispatched by create-subdomain workflow or triggered by "create entity", "model domain", "new value object".

Debugs the full event chain from domain event dispatch through WebSocket delivery to frontend component consumption. Use when events are not reaching the frontend, WebSocket is not updating, handlers are not firing, or real-time updates are broken. Follows the Debug Rule — always trace from origin to UI.

Use when creating application layer artifacts for a NestJS bounded context — use cases, CQRS command/query handlers, DTOs, ports (cross-module interfaces), application services, or read model projections. Supports three patterns: plain UseCase (A), CQRS native (B), and Handler-as-Orchestrator (C).

Orchestrates creation of a NestJS bounded context by dispatching specialized agents per layer (domain, application, infrastructure, presentation). Uses Opus for domain modeling, Sonnet for execution layers. Compatible with GSD workflow (usable as phase execution). Follows TDD, Hexagonal Architecture, DDD, and CQRS.

Use when creating domain layer artifacts for a NestJS bounded context — entities (AggregateRoot), value objects, domain events, repository interfaces, domain services, validators, or data builders. Covers Hexagonal Architecture + DDD patterns with NestJS CQRS native event support.

Use when creating event listeners that react to domain events — same-BC side effects (projections, audit, cache), cross-BC reactions (another bounded context consuming events), or bridge listeners (WebSocket broadcast, RabbitMQ publish, email). Covers listener taxonomy, placement rules, Strategy+Gateway pattern for fan-out, and anti-over-engineering criteria.

Configures a NestJS project to use the nestjs-hexagonal plugin with GSD workflow. Adds skill references to CLAUDE.md, creates GSD-compatible phase templates, and maps GSD phases to plugin agents. Use when setting up a new project with GSD + hexagonal architecture, or when asked to "install hexagonal for GSD", "configure GSD with hexagonal", or "setup nestjs-hexagonal".