layered-architecture

What problem does it solve?

Use when generating or modifying any Spring Boot class — controllers, services, repositories, DTOs, mappers, or configuration. Enforces strict layer separation and prevents business logic from leaking across boundaries.

Core Features & Use Cases

• Layer Rules: REST controller should be HTTP-only; services hold business logic; repositories handle data access; DTOs map responses; mappings should be in dedicated mappers; configuration lives in config packages.
• Controller/Service/Repository guidance: ensure one service per aggregate, avoid business logic in controllers, map entities to DTOs, use @Transactional on services, constructor injection, etc.
• Use Case: When integrating a new module, structure code to align with layers, ensure no coupling across layers, and add tests for layer boundaries.

Quick Start

Describe a Spring Boot project following the Layered Architecture, and I will help enforce and validate the structure across controllers, services, repositories, DTOs, and configurations.