Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Build robust Android and multiplatform apps with Kotlin idioms, coroutines, and null safety.
Build robust Android and multiplatform apps with Kotlin idioms, coroutines, and null safety.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
TopicFileNull safety operators and patternsnullsafety.mdCoroutines, flows, structured concurrencycoroutines.mdCollections, sequences, data classescollections.mdScope functions, extensions, sealed classesidioms.mdJava interop and common Kotlin mistakesinterop.mdAndroid lifecycle, Compose stateandroid.mdDelegation, inline, reified, multiplatformadvanced.md
!! asserts non-null โ crashes on null, use only when you've already checked Platform types from Java are risky โ add null checks or use @Nullable/@NonNull annotations Elvis with return/throw for early exit โ val name = user?.name ?: return
viewModelScope auto-cancels on ViewModel clear โ don't use GlobalScope in Android Structured concurrency: child coroutine failure cancels parent โ use supervisorScope to isolate StateFlow needs initial value and never completes โ SharedFlow for one-shot events Inject dispatchers for testability โ don't hardcode Dispatchers.IO
first() throws on empty โ use firstOrNull() for safe access Only constructor properties in equals/hashCode โ body properties ignored mutableStateListOf for Compose โ wrapping mutableListOf in state won't track changes
Don't nest scope functions โ readability drops fast, extract to named functions Extensions are resolved statically โ not polymorphic, receiver type matters at compile time
repeatOnLifecycle(STARTED) for flow collection โ launchWhenStarted is deprecated remember survives recomposition only โ use rememberSaveable for config changes collectAsStateWithLifecycle is the gold standard โ lifecycle-aware + Compose state
== is structural equality in Kotlin โ === for reference, opposite of Java SAM conversion only for Java interfaces โ Kotlin interfaces need explicit fun interface @JvmStatic, @JvmOverloads, @JvmField for Java-friendly APIs
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.