
Clean Architecture
This walks you through implementing Clean Architecture and Hexagonal Architecture patterns in Spring Boot 3.5+ apps, focusing on keeping your domain logic completely framework-free. You get concrete package structures, instructions for organizing domain entities and value objects separate from JPA entities, and guidance on setting up ports and adapters so infrastructure stays swappable. The skill emphasizes putting business logic in rich domain models rather than anemic services, using Java records for immutable value objects, and includes ArchUnit tests to enforce the dependency rules. It's opinionated about transaction boundaries and includes a validation checklist to grep for Spring annotations leaking into your domain layer, which honestly feels necessary given how easy it is to let framework concerns creep inward.
- skills.sh installs
- 4.1K
- GitHub stars
- 369
- last updated
- Aug 21, 2026
Install
$ npx -y skills add giuseppe-trisciuoglio/developer-kit --skill clean-architecture --agent claude-codeInstalls into .claude/skills of the current project.
Files
Clean Architecture, Hexagonal Architecture & DDD for Spring Boot
Overview
This skill provides comprehensive guidance for implementing Clean Architecture, Hexagonal Architecture (Ports & Adapters), and Domain-Driven Design tactical patterns in Java 21+ Spring Boot 3.5+ applications. It ensures clear separation of concerns, framework-independent domain logic, and highly testable codebases through proper layering and dependency management.
When to Use
- Architecting new Spring Boot applications with clear separation of concerns
- Refactoring tightly coupled code into testable, layered architectures
- Implementing domain logic independent of frameworks and infrastructure
- Designing ports and adapters for swappable implementations
- Applying Domain-Driven Design tactical patterns (entities, value objects, aggregates)
- Creating testable business logic without Spring context dependencies
Instructions
1. Understand the Core Concepts
Clean Architecture Layers (Dependency Rule)
Dependencies flow inward. Inner layers know nothing about outer layers.
Sponsors
Details
- Repository
- github.com/giuseppe-trisciuoglio/developer-kit
- Categories
- Code Review & Quality, Java & JVM, Design & UI/UX
- First seen
- May 16, 2026
More from giuseppe-trisciuoglio/developer-kit
All 102- Prompt Engineering4.1K
- Typescript Security Review4.1K
- Nextjs App Router4K
- Spring Boot Crud Patterns4K
- Chunking Strategy4K
- Spring Boot Event Driven Patterns4K
- Zod Validation Utilities4K
- Nestjs Best Practices4K
- Nestjs Code Review4K
- Spring Boot Cache4K
- Spring Boot Resilience4j3.9K
- Unit Test Service Layer3.9K
- Nextjs Code Review3.9K
- Spring Ai Mcp Server Patterns3.9K
- Unit Test Wiremock Rest Api3.9K
- Spring Boot Actuator3.9K
- Nextjs Authentication3.9K
- Spring Boot Dependency Injection3.9K
- Unit Test Controller Layer3.9K
- Unit Test Parameterized3.9K
- Unit Test Json Serialization3.9K
- Spring Boot Saga Pattern3.9K
- Spring Data Neo4j3.9K
- Unit Test Security Authorization3.9K