16 skills
skills731 ★
Skills for Kotlin, Jetpack Compose, and Android development
checked 4d ago
Catch mistakes in your Kotlin reactive streams
Reviews StateFlow and SharedFlow patterns for common pitfalls: improper state updates, event leaks, replay bugs, and lifecycle mismatches. Suggests idiomatic fixes.
·★710↓0
checked 4d ago
Design a Kotlin Multiplatform API boundary
Sketches the expect/actual structure, source-set layout, and platform-specific stubs for native SDKs, sensors, permissions, or file access without duplicating logic across platforms.
·★710↓0
checked 4d ago
Choose where to put your Compose state
Answer a few questions about your UI element and get a clear recommendation: local remember, hoisted parameter, state holder, or ViewModel—with the tradeoff for each choice.
·★710↓0
checked 4d ago
Audit Compose state for correctness and leaks
Reviews Jetpack Compose code for unsafe state patterns—bare mutable vars, missing remember {} blocks, leaky mutableStateListOf calls—and suggests the right API for each.
·★710↓0
checked 4d ago
Debug why your Compose UI is slow
Reads Jetpack Compose compiler reports, Layout Inspector traces, and composables.txt to pinpoint unnecessary recompositions and suggest which state to move or memoize.
·★710↓0
checked 4d ago
Debug Compose focus and keyboard navigation
Reviews Jetpack Compose UI code for TV, desktop, and keyboard access—catches focus traps, broken D-pad flows, and initial-focus bugs before they ship.
·★710↓0
checked 4d ago
Spot side-effect bugs in Compose code
Reviews Jetpack Compose code for common side-effect pitfalls—missing dependencies, stale closures, lifecycle mismatches—and suggests fixes with explanations.
·★710↓0
checked 4d ago
Write Compose UI tests without the boilerplate
Generates snapshot tests, semantics assertions, and interaction patterns for Jetpack Compose—covering screenshots, focus flow, keyboard input, and state-driven composables.
·★710↓0
checked 4d ago
Spot where @JvmInline value class beats data class
Reviews your Kotlin type declarations and flags places where @JvmInline value class would cut allocations and improve Compose stability—with a concrete refactor for each.
·★710↓0
checked 4d ago
Pick the right Compose animation for your motion
Describes what should move and how, and Claude suggests the exact Compose API (AnimatedVisibility, animate*AsState, rememberTransition) with boilerplate code ready to paste.
·★710↓0
checked 4d ago
Spot layout bugs in Compose code
Reviews Compose modifier chains and layout decisions, catching common mistakes in constraint logic, conditional wrappers, and hardcoded sizing that break on different screens.
·★710↓0
checked 4d ago
Refactor a messy Compose component into slots
Takes a Compose component bloated with boolean flags and content params, diagrams the variable regions, and prescribes a slot-based API that scales without prop explosion.
·★710↓0
checked 4d ago
Debug why your Compose functions keep recomposing
Reads your composable code and compiler reports, identifies unstable parameters and state classes, and explains which parameters force recomposition and how to stabilize them.
·★710↓0
checked 4d ago
Spot Compose state bugs that only show at runtime
Reviews Jetpack Compose code for deferred-read antipatterns — state captured in the wrong phase, reads across composable boundaries, or layout-phase writes that skip recomposition.
·★710↓0
checked 4d ago
Spot concurrency bugs in Kotlin code
Reviews Kotlin code for common structured-concurrency violations: leaked scopes, runBlocking in the wrong place, caught exceptions that swallow cancellation, orphaned coroutines.
·★710↓0
checked 4d ago
Split a tangled Compose screen into state and UI
Refactors a screen-level composable that mixes state collection, navigation, and layout into separate holder and UI functions—reducing noise and making the layout readable.
·★710↓0