java-lombok

Apply Lombok annotations like @Delegate, @Builder, and @UtilityClass to reduce Java boilerplate.

4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/cuioss/plan-marshall --skill java-lombok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: java-lombok
Source: https://github.com/cuioss/plan-marshall/tree/main/marketplace/bundles/pm-dev-java/skills/java-lombok
Command: npx skills add https://github.com/cuioss/plan-marshall --skill java-lombok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lombok patterns reduce boilerplate code while maintaining code quality and testability.

Core Features & Use Cases

  • @Delegate - Delegation Over Inheritance: Use Lombok's @Delegate to wrap implementations and compose behavior without inheritance.
  • @Builder - Complex Object Construction: Generate builders for types with many parameters and provide defaults (best suited for classes; records have limitations).
  • @Value / @Data / @UtilityClass: Prefer records for immutable values, use @Data sparingly for mutable beans, and apply @UtilityClass to create a static utility container.
  • When to use builders with records vs classes: Records + @Builder are ideal for immutable types with many fields, with defaults handled via a manual builder when necessary; Classes + @Builder are preferred when you need @Builder.Default, toBuilder, or Jackson annotations.

Quick Start

Apply Lombok patterns such as @Delegate, @Builder, and @UtilityClass to reduce boilerplate in your Java codebase.

Frequently Asked Questions about java-lombok

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce boilerplate code in Java using Lombok annotations?

Reduce Java boilerplate by applying Lombok patterns like @Data for mutable beans, @Value for immutable objects, and @UtilityClass to generate static utility containers, ensuring code remains readable and maintainable.

When should I use the Lombok @Builder annotation with records versus classes?

Use @Builder with Java records for immutable types with many fields, handling defaults manually. Use @Builder with classes when you need @Builder.Default, toBuilder, or Jackson annotations.

What is the best way to implement delegation over inheritance in Java?

Implement delegation over inheritance in Java by applying Lombok's @Delegate annotation to wrap implementations and compose behavior dynamically without relying on class inheritance.

Should I use @Data or @Value for immutable data classes in Java?

Prefer Java records or Lombok's @Value for immutable data classes. Use @Data sparingly, reserving it primarily for mutable beans where setters are explicitly required.

What are the limitations of using Lombok @Builder with Java records?

Limitations of @Builder with Java records include restricted support for @Builder.Default and toBuilder. When these features are needed, using traditional classes with @Builder is preferred.