Review and fix Kotlin Coroutines issues in Android codebases by applying structured concurrency, lifecycle safety, proper scoping, and modern best practices with minimal behavior changes.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionkotlin-concurrency-expertExecute the skills CLI command in your project's root directory to begin installation:
Fetches kotlin-concurrency-expert from new-silvermoon/awesome-android-agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate kotlin-concurrency-expert. Access via /kotlin-concurrency-expert in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
2
total installs
2
this week
642
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
642
stars
Review and fix Kotlin Coroutines issues in Android codebases by applying structured concurrency, lifecycle safety, proper scoping, and modern best practices with minimal behavior changes.
kotlinx-coroutines-android version, lifecycle-runtime-ktx version.viewModelScope, lifecycleScope, custom scope, or none).Dispatchers.Main) or intended to run off the main thread (Dispatchers.IO, Dispatchers.Default).Prefer edits that preserve existing behavior while satisfying structured concurrency and lifecycle safety.
Common fixes:
withContext(Dispatchers.IO) or Dispatchers.Default; ensure suspend functions are main-safe.GlobalScope with a lifecycle-bound scope (viewModelScope, lifecycleScope, or injected applicationScope).launchWhenStarted with repeatOnLifecycle(Lifecycle.State.STARTED).MutableStateFlow / MutableSharedFlow; expose read-only StateFlow or Flow.catch (e: Exception) blocks rethrow CancellationException.ensureActive() or yield() in tight loops for cooperative cancellation.callbackFlow with proper awaitClose cleanup.CoroutineDispatcher via constructor for testability.// CORRECT: Inject dispatcher
class UserRepository(
private val ioDispatcher: CoroutineDispatcher = Dispatchers.IO
) {
suspend fun fetchUser() = withContext(ioDispatcher) { ... }
}
// INCORRECT: Hardcoded dispatcher
class UserRepository {
suspend fun fetchUser() = withContext(Dispatchers.IO) { ... }
}
// CORRECT: Use repeatOnLifecycle
viewLifecycleOwner.lifecycleScope.launch {
viewLifecycleOwner.repeatOnLifecycle(Lifecycle.State.STARTED) {
viewModel.uiState.collect { state -> updateUI(state) }
}
}
// INCORRECT: Direct collection (unsafe, deprecated)
lifecycleScope.launchWhenStarted {
viewModel.uiState.collect { state -> updateUI(state) }
}
// CORRECT: Expose read-only StateFlow
class MyViewModel : ViewModel() {
private val _uiState = MutableStateFlow(UiState())
val uiState: StateFlow<UiState> = _uiState.asStateFlow()
}
// INCORRECT: Exposed mutable state
class MyViewModel : ViewModel() {
val uiState = MutableStateFlow(UiState()) // Leaks mutability
}
// CORRECT: Rethrow CancellationException
try {
doSuspendWork()
} catch (e: CancellationException) {
throw e // Must rethrow!
} catch (e: Exception) {
handleError(e)
}
// INCORRECT: Swallows cancellation
try {
doSuspendWork()
} catch (e: Exception) {
handleError(e) // CancellationException swallowed!
}
// CORRECT: Check for cancellation in tight loops
suspend fun processLargeList(items: List<Item>) {
items.forEach { item ->
ensureActive() // Check cancellation
processItem(item)
}
}
// INCORRECT: Non-cooperative (ignores cancellation)
suspend fun processLargeList(items: List<Item>) {
items.forEach { item ->
processItem(item) // Never checks cancellation
}
}
// CORRECT: callbackFlow with awaitClose
fun locationUpdates(): Flow<Location> = callbackFlow {
val listener = LocationListener { location ->
trySend(location)
}
locationManager.requestLocationUpdates(listener)
awaitClose { locationManager.removeUpdates(listener) }
}
| Scope | Use When | Lifecycle |
|---|---|---|
viewModelScope |
ViewModel operations | Cleared with ViewModel |
lifecycleScope |
UI operations in Activity/Fragment | Destroyed with lifecycle owner |
repeatOnLifecycle |
Flow collection in UI | Started/Stopped with lifecycle state |
applicationScope (injected) |
App-wide background work | Application lifetime |
GlobalScope |
NEVER USE | Breaks structured concurrency |
@Test
fun `loading data updates state`() = runTest {
val testDispatcher = StandardTestDispatcher(testScheduler)
val repository = FakeRepository()
val viewModel = MyViewModel(repository, testDispatcher)
viewModel.loadData()
advanceUntilIdle()
assertEquals(UiState.Success(data), viewModel.uiState.value)
}
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
erichowens/some_claude_skills
sickn33/antigravity-awesome-skills
erichowens/some_claude_skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
kotlin-concurrency-expert reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in kotlin-concurrency-expert — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
kotlin-concurrency-expert has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for kotlin-concurrency-expert matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: kotlin-concurrency-expert is focused, and the summary matches what you get after install.
kotlin-concurrency-expert fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for kotlin-concurrency-expert matched our evaluation — installs cleanly and behaves as described in the markdown.
kotlin-concurrency-expert has been reliable in day-to-day use. Documentation quality is above average for community skills.
kotlin-concurrency-expert has been reliable in day-to-day use. Documentation quality is above average for community skills.
kotlin-concurrency-expert fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 70