What problem does it solve?
Kotlin teams often struggle to maintain consistent idiomatic code style and design practices across files and modules; this skill provides concrete guidance on file organization, type design, constructors, extensions, nullability, serialization, coroutines, Flow, and test style to reduce cognitive load during reviews.
Core Features & Use Cases
- Guidelines for Kotlin file organization and package structure to improve readability
- Rules for type design, data classes, constructors, factories, and visibility
- Recommendations for extension functions placement and helper ownership
- Best practices for nullability, serialization, coroutines, and Flow usage
- Kotlin unit and integration test style guidance, excluding Cucumber/BDD
Quick Start
Provide idiomatic Kotlin guidance for a given module to improve readability and maintainability.