What problem does it solve? Manually writing DTO classes for every domain is repetitive and error-prone, and inconsistent naming or annotation placement breaks team conventions. This Skill generates convention-compliant Request/Response DTO classes for Spring Boot projects after a short interview about the target domain. ## Core Features & Use Cases - Convention-Enforced Generation: Creates {Domain}Request.java and {Domain}Response.java files that follow the common-rule.md conventions, with no annotations on outer classes and @Data only on inner static classes. - Standardized Naming: Uses function-based names for Request inner classes (Save, Update, Login, Join) and data-scope names for Response inner classes (Max, Min, Detail, Option, DTO). - Entity-to-DTO Conversion: Includes constructors or static factory methods so entities are never exposed directly to controllers. - Use Case: When adding a new Board domain to a Spring Boot project, ask for its DTOs and receive ready-to-use BoardRequest.java and BoardResponse.java files with Save, Update, and Detail classes already wired to the Board entity. ## Quick Start Ask the assistant to create DTO classes for your domain, for example by saying "make DTOs for the Board domain with Save and Detail classes".
