Kotlin Code Style

Use the sections relevant to the Kotlin decision being made. Follow local conventions where they differ, and distinguish application internals from public library contracts when that affects the answer.

For formatting or comment-only work, go directly to Format and verify. Apply ownership, concurrency, and API guidance only to the requested change.

Related guidance

Load another skill only when the task needs its policies and they are not already available:

• code-practice: shared ownership, compound state, trust boundaries, error handling, or test design. New or changed code-based tests retain its explicit Given, When, and Then comment sections.
• component-collaboration-architecture: direct calls versus events, projections, or ownership across components.
• spring-application-code-style: controllers, transactions, bean wiring, or Spring-managed lifecycle behavior.
• kotlin-cucumber-tests: feature files, step definitions, hooks, and BDD scenarios.

Files and types