How does this skill handle logging?

It specifically prohibits the use of Lombok logging annotations like @Slf4j in favor of project-specific implementations like CuiLogger to ensure architectural consistency.

Why use @Delegate instead of inheritance?

The @Delegate pattern promotes composition over inheritance, allowing for more flexible, decoupled, and testable code by wrapping implementations rather than extending them.

Can this skill help migrate to Java Records?

Yes, it includes detailed comparison guidance on when to use native Java Records versus Lombok @Value based on the Java version and required features like builders.

Does it support complex builder patterns?

Yes, it provides patterns for @Builder with @Singular collections and @Builder.Default values for robust and flexible object creation.

Java Lombok Development

Name: Java Lombok Development
Author: cuioss

bycuioss

API Development

Reduces Java boilerplate code by enforcing standardized patterns for immutability, delegation, and object construction using Project Lombok.

About

This skill empowers Claude to implement high-quality Java code using Project Lombok, focusing on reducing boilerplate while maintaining strict architectural standards. It provides specific implementation patterns for delegation over inheritance using @Delegate, immutable data structures with @Value, and sophisticated object construction via @Builder with singular collection support. Additionally, it ensures project consistency by enforcing specific logging implementations and providing clear guidance on when to transition from Lombok to native Java Records in modern environments.

Key Features

Configures complex object construction with @Singular and @Builder.Default
Generates immutable value objects and DTOs using @Value and @Builder
Implements delegation patterns with @Delegate to avoid tight inheritance coupling
0 GitHub stars
Standardizes utility class creation using the @UtilityClass annotation
Provides decision matrices for choosing between Lombok annotations and Java Records

Use Cases

Designing immutable configuration objects and API response DTOs
Implementing the decorator or proxy pattern via delegation instead of inheritance
Refactoring legacy Java classes to reduce boilerplate and improve readability

About

Key Features

Configures complex object construction with @Singular and @Builder.Default
Generates immutable value objects and DTOs using @Value and @Builder
Implements delegation patterns with @Delegate to avoid tight inheritance coupling
0 GitHub stars
Standardizes utility class creation using the @UtilityClass annotation
Provides decision matrices for choosing between Lombok annotations and Java Records

Use Cases

Designing immutable configuration objects and API response DTOs
Implementing the decorator or proxy pattern via delegation instead of inheritance
Refactoring legacy Java classes to reduce boilerplate and improve readability