Lombok Coding Conventions Training

Key things the skill must make very clear:

• Never write a constructor/getter/setter/toString/equals/hashCode by hand when an annotation will generate it
• @Inject/@Autowired constructors go via onConstructor_ on @RequiredArgsConstructor
• Manual Logger fields must be replaced with the matching @Log variant (@Slf4j, @Log4j2, etc.)
• Utility classes use @UtilityClass; exception classes use @StandardException
• lombok.val / lombok.var must never be used — use Java's native var instead

Step 2: Validate with test cases

After regenerating, validate the skill using the test cases in evals/evals.json.

For each test case, spawn a subagent that:

1. Reads the generated skill from plugins/conventions/skills/lombok-coding-conventions/SKILL.md
2. Reads any input files specified in the test case
3. Completes the task described in the prompt, following the skill's conventions
4. Writes output Java files to a workspace directory

Then run the shared grading script against the outputs:

cd plugins/training
python -m shared.grade <workspace-dir>

The script checks:

• No hand-written getters/setters
• No hand-written toString / equals / hashCode
• Lombok annotations are actually used
• No manual Logger field when @Slf4j (or variant) applies
• @Inject/@Autowired constructors use onConstructor_
• Exception classes use @StandardException; utility classes use @UtilityClass
• No lombok.val / lombok.var imports

Test cases

1. Refactor UserDto — manual getters, setters, constructor, toString, equals/hashCode → @Data (or the equivalent combination)
2. Refactor GreetingService — hand-written @Inject constructor and manual SLF4J Logger field → @RequiredArgsConstructor(onConstructor_ = @Inject) + @Slf4j
3. Greenfield utilities — create a StringUtils utility class and a ValidationException exception class using @UtilityClass and @StandardException

Input files for refactoring tests are in evals/files/.

Conventions reference

The authoritative conventions are in references/conventions.md.