Enforce OpenAPI annotations and DTO conversion in Java Spring controllers.
npx skills add https://github.com/GreenFirst-kr/green_first_be --skill web-layer
Please help me install this Agent Skill. Skill: web-layer Source: https://github.com/GreenFirst-kr/green_first_be/tree/main/.claude/skills/web-layer Command: npx skills add https://github.com/GreenFirst-kr/green_first_be --skill web-layer
This skill guides teams to implement or review the web-layer (controller) code with a consistent, well-scoped approach, enforcing patterns such as direct OpenAPI annotations and standardized response handling.
Implement or review a new web-layer controller using GetXxxController or CreateXxxController patterns, with OpenAPI annotations on methods and responses wrapped in BaseResponse.
High-intent search queries and answers about installing and using this skill.
Spring Boot controllers should use direct OpenAPI annotations on methods, avoid API spec interfaces, and handle DTO conversion via static from() methods in response classes to keep controllers clean. Responses are wrapped in BaseResponse for consistent web-layer contracts.
The best way to organize web-layer controllers is using explicit naming conventions like GetXxxController or CreateXxxController, separating controller, service, and domain layers, and avoiding API spec directories like api/ or api/spec/ to improve maintainability.
You should avoid using API spec interfaces for Spring REST controllers. Instead, apply OpenAPI annotations directly on controller methods to enforce well-structured REST endpoints and maintain a clear base for web-layer contracts.
Validate requests in Spring web-layer controllers using Bean Validation with @Valid. Convert DTOs by implementing static from() methods within response classes to move conversion logic out of the controller and into the DTO itself.
Wrapping Spring controller responses in BaseResponse ensures standardized response handling across all web-layer REST endpoints. This approach enforces consistent controller practices and provides a uniform contract for API consumers.
Yes, this web-layer pattern enforces a clear separation between controller, service, and domain layers. By using static from() methods for DTO conversion and avoiding API spec interfaces, it keeps controller logic focused on routing and web-layer contracts.
anishi1222Generate a Spring Boot Java project skeleton with configurable name, version, and dependencies.
Faouzi91Generate fully annotated Spring Boot REST controllers with CRUD endpoints and OpenAPI documentation.
cescrafliGuide Spring Boot backend architecture with layered controller-service-repository patterns.
AmplicodeGenerate a Spring REST controller with CRUD endpoints from a Spring Data repository.
