design-patterns

Applying GoF design patterns in Kotlin without over-engineering involves mapping classic class-based structures to idiomatic Kotlin constructs like sealed interfaces and higher-order functions. This skill provides a framework to favor language-native solutions over complex hierarchies.

The best way to refactor a Strategy pattern into idiomatic Kotlin is to replace verbose class hierarchies with higher-order functions and interface delegation. This skill analyzes your structure to determine if class-based patterns can dissolve into native language features.

You need sealed classes in Kotlin instead of traditional Factory or Decorator patterns when managing restricted domain hierarchies. This skill evaluates pattern necessity against language-native solutions to determine if sealed interfaces provide a safer, more idiomatic alternative.

Yes, you can use this skill to evaluate architectural decisions and enforce composition-over-inheritance during code reviews. It provides a framework for structuring object collaborations while maintaining immutability and domain-driven design constraints.

Your Kotlin refactoring might still require complex object collaborations if pattern necessity outweighs language-native idioms. This skill provides a decision framework to evaluate when classic GoF patterns are genuinely needed versus when features like interface delegation suffice.