Kotlin

What This Skill Does

The Kotlin skill provides OpenClaw with an expert-level understanding of the Kotlin programming language, specifically tailored for Android development and Kotlin Multiplatform projects. It acts as an intelligent pair programmer that enforces idiomatic practices, ensures rigorous null safety, and manages complex asynchronous workflows using Kotlin Coroutines and Flows. By integrating this skill, your agent can effectively refactor legacy Java code, implement state management in Jetpack Compose, and troubleshoot concurrency issues that often plague high-performance applications.

Installation

To install this skill, run the following command in your OpenClaw terminal: clawhub install openclaw/skills/skills/ivangdavila/kotlin

Use Cases

1. Legacy Refactoring: Convert complex Java-based Android logic into modern, null-safe Kotlin code while maintaining binary compatibility using @JvmOverloads and @JvmStatic.
2. State Management: Implement lifecycle-aware state collection in Jetpack Compose using collectAsStateWithLifecycle to prevent resource leaks and ensure UI consistency.
3. Asynchronous Architecture: Design scalable data layers using StateFlow and SharedFlow, ensuring correct usage of viewModelScope and structured concurrency principles.
4. Code Auditing: Analyze existing codebases for common pitfalls, such as improper use of !! (non-null assertion), incorrect scope function nesting, or memory-leaking coroutine scopes.

Example Prompts

1. "Refactor this Java service class to Kotlin, ensuring all platform types are handled safely and exposing it correctly to Java consumers."
2. "Help me identify why my Jetpack Compose UI isn't updating correctly when the underlying StateFlow changes in my ViewModel."
3. "Write a clean implementation of a Repository pattern using Flow and Coroutines that handles data fetching and error states robustly."

Tips & Limitations

• Context is Key: Always provide the surrounding class or scope context when asking for refactoring help; Kotlin’s behavior often depends on the specific lifecycle scope (e.g., viewModelScope vs. lifecycleScope).
• Prefer firstOrNull(): Avoid first() on collections unless you are absolutely certain of the contents; firstOrNull() prevents common runtime crashes.
• Avoid GlobalScope: Never use GlobalScope in Android applications as it ignores lifecycle management and leads to memory leaks.
• Polymorphism Awareness: Remember that Kotlin extension functions are resolved statically. If you are overriding behavior in a subclass, use standard member functions instead of extensions.