Java Lombok Skill

REFERENCE MODE: This skill provides reference material. Load specific standards on-demand based on current task.

Lombok standards for reducing boilerplate code while maintaining code quality and testability.

Prerequisites

This skill applies to Java projects using Project Lombok for boilerplate reduction.

Workflow

Step 1: Load Core Annotations

Important: Load this standard for any Lombok work involving @Delegate, @Builder, @Value, @Data, or @UtilityClass.

Read: standards/lombok-core-annotations.md

This provides rules for:

• @Delegate for delegation over inheritance
• @Builder with records vs classes (including @Builder.Default limitations)
• @Value vs records decision guidance
• @Data for mutable objects
• @UtilityClass for static method classes

Step 2: Load Canonical Methods (As Needed)

Load for entity/bean work involving @EqualsAndHashCode, @ToString, @Getter, @Setter:

Read: standards/lombok-canonical-methods.md

This provides rules for:

• @EqualsAndHashCode with business keys and inheritance
• @ToString with sensitive field exclusion
• @Getter / @Setter for mutable beans (JPA entities)
• Common pitfalls table

Key Decision Guide

Scenario	Recommendation
Immutable data carrier	Java record (not @Value)
4+ constructor parameters	@Builder
Need @Builder.Default or toBuilder	Class with @Builder
Delegation over inheritance	@Delegate
JPA entity with business key	@Getter + @Setter + @EqualsAndHashCode(of = ...)
Static utility methods	@UtilityClass

Known gaps in this guidance

Recorded so they are not mistaken for settled decisions — these are gaps, not rules:

• The decision guide is silent on parameter contracts via Lombok @NonNull — it gives no guidance on when to annotate a method or constructor parameter with @NonNull to generate an entry null-check, versus relying on @NullMarked + JSpecify (see pm-dev-java:java-null-safety).
• There is no trigger for auditing utility-class eligibility — the guide recommends @UtilityClass for static-method classes but names no signal for when to check whether an existing class (all static methods, no instance state) should become one.

Related Skills

• pm-dev-java:java-core - Core Java patterns, records migration
• pm-dev-java:java-null-safety - Null safety with Lombok