What problem does it solve? Writing new Service classes by hand often leads to inconsistent annotation ordering, missing transaction boundaries, and accidental exposure of raw JPA entities to controllers. This Skill generates Service classes that strictly follow the project's common-rule.md conventions. ## Core Features & Use Cases - Convention-Compliant Generation: Produces Service classes with the required annotation order (@Transactional(readOnly = true), @RequiredArgsConstructor, @Service) and per-method write transactions. - Guided Interview: Collects the target domain, required business methods, and session-user dependencies through a short one-question-at-a-time interview before generating code. - DTO Enforcement: Ensures Services return DTOs instead of raw entities, and warns when prerequisite Repository or DTO classes do not exist. - Use Case: When adding a new Board domain to a Spring Boot project, ask for a service with list, detail, create, update, and delete methods, and receive a ready-to-use BoardService.java placed in the correct package. ## Quick Start Ask the assistant to create a service for your domain, for example by saying "Board 도메인 서비스 만들어줘" with the business methods you need.