What problem does it solve? Spring Boot projects often suffer from tangled layers where domain logic leaks into controllers, JPA annotations pollute business entities, and framework dependencies make code untestable. This Skill enforces a strict layered architecture so business rules stay independent of frameworks. ## Core Features & Use Cases - Layered Dependency Rules: Defines the Dependency Rule with clear import boundaries across Domain, Application, Infrastructure, and Presentation layers. - Ports & Adapters Patterns: Provides concrete templates for repository adapters, port interfaces, JPA entity separation, and domain-to-JPA mapping. - Testing & Anti-Pattern Guidance: Includes per-layer testing strategies, common mistake examples, a standard package structure, and a compliance checklist. - Use Case: When building a new Spring Boot microservice, use this Skill to scaffold the correct package structure, keep domain entities free of JPA/Spring annotations, and implement repository adapters that map between domain and persistence models. ## Quick Start Ask the AI to review or generate a Spring Boot feature following Clean Architecture with separated domain, application, infrastructure, and presentation layers.
