- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add rrezartprebreza/spring-boot-skills --skill layered-architecture -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add rrezartprebreza/spring-boot-skills --skill layered-architecture -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add rrezartprebreza/spring-boot-skills --skill layered-architecture -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add rrezartprebreza/spring-boot-skills --skill layered-architecture -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/rrezartprebreza/spring-boot-skills/tree/HEAD/skills/spring-boot-3/layered-architectureDel publicador
@RestController ← HTTP only. No business logic. No JPA entities in responses.
↓ DTOs
@Service ← All business logic lives here. Orchestrates repositories.
↓ Domain objects / Entities
@Repository ← Data access only. No business logic. Returns entities or projections.
↓ JPA / JDBC
Database
@Valid), returning responses@Entity classes directly — always map to response DTOs@Repository — always goes through a @Service@ControllerAdvice, never try/catch in controllers// GOOD
@PostMapping("/orders")
public ResponseEntity<OrderResponse> createOrder(@Valid @RequestBody CreateOrderRequest request) {
Order order = orderService.createOrder(request);
return ResponseEntity.status(HttpStatus.CREATED).body(OrderResponse.from(order));
}
// BAD — business logic in controller
@PostMapping("/orders")
public ResponseEntity<Order> createOrder(@RequestBody CreateOrderRequest request) {
if (request.getItems().isEmpty()) throw new RuntimeException("No items");
Order order = orderRepository.save(new Order(request)); // direct repo access
return ResponseEntity.ok(order); // returning entity
}
@Transactional lives here, not in controllers or repositories@Autowired field injectionHttpServletRequest / HttpServletResponse// GOOD
@Service
@RequiredArgsConstructor
public class OrderService {
private final OrderRepository orderRepository;
private final InventoryService inventoryService;
@Transactional
public Order createOrder(CreateOrderRequest request) {
inventoryService.reserve(request.items()); // records use accessor names, not getX()
Order order = Order.from(request);
return orderRepository.save(order);
}
}
// BAD — field injection, HTTP concern in service
@Service
public class OrderService {
@Autowired private OrderRepository orderRepository;
public ResponseEntity<Order> createOrder(...) { ... } // HTTP type in service
}
JpaRepository<Entity, ID> or CrudRepository@Query or query derivation — no raw SQL unless unavoidableObject[]@NotNull, @Size, etc.) on Request DTOs onlyResponseDto.from(Entity entity) for mapping// GOOD
public record OrderResponse(UUID id, String status, List<LineItemResponse> items, Instant createdAt) {
public static OrderResponse from(Order order) {
return new OrderResponse(order.getId(), order.getStatus().name(),
order.getItems().stream().map(LineItemResponse::from).toList(),
order.getCreatedAt());
}
}
OrderResponse.from(order))Order.from(request)) or a mapper class.stream().map(OrderResponse::from).toList() — never manual loops// GOOD — dedicated mapper for complex mappings
public class OrderMapper {
public static OrderResponse toResponse(Order order) {
return new OrderResponse(
order.getId(),
order.getStatus().name(),
order.getItems().stream().map(OrderMapper::toLineItem).toList(),
order.getCreatedAt()
);
}
public static Order toEntity(CreateOrderRequest request, User user) {
Order order = Order.create(request.customerEmail(), user);
request.items().forEach(item ->
order.addItem(item.productId(), item.quantity()));
return order;
}
private static LineItemResponse toLineItem(OrderItem item) {
return new LineItemResponse(item.getProductId(), item.getQuantity(), item.getPrice());
}
}
@Configuration classes live in a config/ package — never in service/ or controller/@ConfigurationProperties for type-safe config — never raw @Value for groups of related settings@Slf4j — never System.out.println@Valid on controller parameters, custom validators as @Component@RestControllerAdvice class, never try/catch in controllers@CreatedDate / @LastModifiedDate with @EnableJpaAuditing@Transactional on controllers — move it to services@Autowired field injection — always use constructor injection (@RequiredArgsConstructor)List<Entity> from controllers — always map to List<ResponseDto>OrderAndInventoryService god classes — split by aggregate@Configuration classes that depend on @Service beans — configuration should only wire infrastructure>
---name: layered-architecturedescription: >---# skills/spring-boot-3/layered-architecture/SKILL.mdPreguntas frecuentes
Descarga skills/spring-boot-3/layered-architecture/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/rrezartprebreza/spring-boot-skills.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.