kotlin-idiomatic-refactorer-spring-aware

Refactor Kotlin toward immutable constructor injection and exhaustive when expressions while preserving Spring proxy compatibility. This Skill guides safe incremental patches that maintain proxy behavior during Java-flavored Kotlin cleanup.

No, prefer data classes for transport or value models rather than JPA entities. Use sealed classes or sealed interfaces for closed result domains to keep domain modeling expressive while maintaining persistence compatibility.

Ensure null-safety by avoiding !! where possible and considering value classes with explicit validation. This Skill replaces forced null assertions with safer idiomatic patterns while maintaining configuration binding and Jackson serialization.

Replacing imperative branching with when expressions does not break Jackson serialization. This Skill ensures compatibility with Jackson serialization and configuration binding while applying exhaustive reasoning for better readability.

Avoid idiomatic refactoring when it compromises Spring proxy behavior, JPA persistence, or public contracts. Use this Skill to apply a verification strategy that identifies limitations and ensures refactors remain safe for existing tests.