kotlin-backend-conventions

Follow the three reference guides: file structure and imports, naming and function design, and null safety with project practices. Key rules include 4-space indentation, 120-character line width, no wildcard imports, and named arguments for multi-parameter calls.

Package names are all lowercase without underscores, classes use PascalCase, and functions, properties, and local variables use lowerCamelCase. Boolean values should prefer prefixes like is, has, can, or should.

Use named arguments when a call has multiple parameters that are easy to confuse, and prefer them when instantiating data classes. This improves readability and reduces maintenance errors compared to positional arguments of the same type.

No, it focuses only on Kotlin language-level conventions such as formatting, naming, and null safety. Spring Boot framework usage, backend service layering, and unit testing practices are handled by separate skills.

The !! operator should only be used when there is a well-justified reason. Prefer safe calls (?.), the Elvis operator (?:), and the type system to express nullability, and use explicit exceptions or result types for failure scenarios.