What problem does it solve? Inconsistent Kotlin code style across a project creates technical debt, noisy diffs, and lint warnings. This Skill gives AI agents and developers a strict, enforceable checklist based on the Official Kotlin Coding Conventions so every code change in the MeteoMartoCompose project follows the same layout, naming, and formatting rules. ## Core Features & Use Cases - Class Layout Enforcement: Mandates declaration order (properties, constructors, functions, companion object last) for readable, predictable classes. - Naming & Modifier Rules: Defines PascalCase, camelCase, UPPER_SNAKE_CASE conventions and the canonical modifier order (e.g., suspend operator fun). - Import & Formatting Hygiene: Bans wildcard imports, requires removal of unused imports, enforces 4-space indentation, trailing commas, and extraction of magic literals into centralized constants. - Use Case: When an AI agent implements a new feature like a high-temperature notification service, it verifies the generated Kotlin code against this checklist as part of the Definition of Done before submitting the change. ## Quick Start Review my new Kotlin class and fix any violations of the project's coding conventions, including companion object placement, modifier order, and wildcard imports.
