Skip to content
cccskills
FreePublished on GitHub

spring-boot-architecture

Structure Spring Boot 3+ projects with feature packaging and clean layering. Use when structuring Spring Boot 3 projects, defining layers, or applying architecture patterns.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (3)

  • SKILL.md2.5 KB
  • evals/evals.json2.3 KB
  • references/implementation.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Spring Boot Architecture Standards

Priority: P0 (CRITICAL)

Organize by Feature

  • Package by Feature: Prefer com.app.feature (e.g., user, order) over technical layers (controllers) for scalability.
  • Dependency Rule: Outer layers (Web) depend on Inner (Service). Inner layers MUST NOT depend on Outer.
  • DTO Pattern: ALWAYS use DTOs for API inputs/outputs. NEVER return @Entity directly.
  • Java Records: Use record for DTOs to ensure immutability (Java 17+).

See implementation examples for Java Record DTOs, controller patterns, and global exception handling.

Define Layer Responsibilities

  1. Controller (Web): Handle HTTP, Validation (@Valid), DTO mapping. Delegate logic to Service.
  2. Service (Business): Transaction boundaries, orchestration. Returns Domain/DTOs.
  3. Repository (Data): Database interactions only. Returns Entities/Projections.

Design API Layer

  • Global Error Handling: Use @RestControllerAdvice with ProblemDetails (RFC 7807).
  • Validation: Use Jakarta Bean Validation (@NotNull, @Size) on DTOs.
  • Response: Use ResponseEntity for explicit status or ResponseStatusException.

Verification Checklist (Mandatory)

  • No Entities in API: all API responses using DTOs/Records instead of JPA Entities?
  • Validation: @Valid and Jakarta Bean Validation constraints present on all input DTOs?
  • Layer coupling: Services depend on Controllers? (Prohibited)
  • Transactionality: business transactions correctly bounded with @Transactional in Service layer?
  • Error Details: ProblemDetails used for consistent error responses?

Anti-Patterns

  • No Fat Controllers: Move business logic to Services.
  • No Leaking Entities: Use DTOs instead of JPA Entities in APIs.
  • No Circular Dependencies: Use Events or refactor to decouple services.
  • No God Classes: Split large services into single-responsibility components.

References

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their specific skills.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test recipes to their specific skills.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

See all skills by HoangNguyen0403

Report a problem with this skill