Rust Lombok Macros

Treat lombok-macros as a procedural-macro dependency and API generator, not as a complete Rust equivalent of Java Lombok. Confirm every generated method's signature, visibility, failure behavior, and compatibility boundary before removing boilerplate.

Scope

Use this skill for:

• DTOs, configuration snapshots, internal messages, test fixtures, and other data carriers where every field combination is valid;
• reducing mechanical methods with Getter, GetterMut, Setter, Data, or New;
• excluding explicitly identified sensitive fields with CustomDebug;
• reviewing existing attributes, upgrading the crate, or migrating handwritten methods.

Do not generate methods blindly for:

• domain entities, value objects, or security boundaries that require validation;
• methods with stable public contracts, custom errors, auditing, or side effects;
• Option or Result access paths that must preserve absence or error information;
• builders, default-value policies, serialization, comparisons, or hashing; version 2.0.32 does not provide these capabilities.