What problem does it solve? Writing NestJS backend modules by hand often leads to inconsistent layering, business logic leaking into controllers, and ad-hoc error handling. This Skill standardizes the implementation of controllers, services, repositories, DTOs, and mappers so every module follows Clean Architecture, the Result pattern, and X-Road packaging conventions. ## Core Features & Use Cases - Layered module implementation: Generates domain services returning Result<T, E>, presentation-layer DTOs with class-validator decorators, static mappers, and controllers with @TraceBreadcrumb auditing. - Standardized error mapping: Translates typed DomainError instances into HTTP exceptions via ErrorMapperToHttp with a defined status-code catalog (404, 401, 403, 409, 422, 400). - X-Road interoperability: Provides an interceptor template that wraps responses with X-Road headers for service bus publication. - Use Case: After nestjs-architect defines a module structure, ask the agent to implement the demand feature; it writes the controller, service, repository, DTOs, and mappers directly to disk and reports a synthetic summary without dumping code into the chat. ## Quick Start Ask the agent to implement the controller, service, DTOs, and mappers for a specific NestJS feature following the Result pattern and Clean Architecture layers.
