Communitygithub.com

Kotlin Coroutines y Flows

Patrones de Coroutines y Flow de Kotlin para Android y KMP: concurrencia estructurada, operadores de Flow, StateFlow, manejo de errores y pruebas. Utilízalo al escribir código con coroutines o Flow en Android o KMP, o al depurar cancelación y concurrencia.

¿Qué es Kotlin Coroutines y Flows?

Este skill proporciona una guía completa y práctica sobre el uso de Kotlin Coroutines y Flow en proyectos de Android y Kotlin Multiplatform (KMP). Abarca desde los fundamentos de la concurrencia estructurada —como la jerarquía de ámbitos y el uso de `coroutineScope` y `supervisorScope` para descomposición paralela— hasta patrones avanzados de Flow reactivo, incluyendo `StateFlow`, `SharedFlow`, operadores como `debounce`, `flatMapLatest` y `retryWhen`. También cubre el manejo adecuado de dispatchers (`Dispatchers.Default`, `Dispatchers.IO`, `Dispatchers.Main`), la cancelación cooperativa con `ensureActive()` y `try/finally`, y estrategias de pruebas unitarias con Turbine y `TestDispatcher`. Está diseñado para ayudar a desarrolladores a escribir código asíncrono robusto, evitable fugas de corrutinas y aplicar patrones modernos de arquitectura limpia en Android y KMP.

Compatible con~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/affaan-m/everything-claude-code/tree/main/skills/kotlin-coroutines-flows

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

Kotlin Coroutines & Flows

Patrones para concurrencia estructurada, flujos reactivos basados en Flow y pruebas de coroutines en proyectos Android y Kotlin Multiplatform.

Cuándo activarlo

  • Al escribir código asíncrono con coroutines de Kotlin
  • Al usar Flow, StateFlow o SharedFlow para datos reactivos
  • Al manejar operaciones concurrentes (carga paralela, debounce, reintento)
  • Al probar coroutines y Flows
  • Al gestionar ámbitos de coroutines y cancelación

Concurrencia Estructurada

Jerarquía de Ámbitos

Application
  └── viewModelScope (ViewModel)
        └── coroutineScope { } (hijo estructurado)
              ├── async { } (tarea concurrente)
              └── async { } (tarea concurrente)

Usa siempre concurrencia estructurada — nunca GlobalScope:

// MAL
GlobalScope.launch { fetchData() }

// BIEN — limitado al ciclo de vida del ViewModel
viewModelScope.launch { fetchData() }

// BIEN — limitado al ciclo de vida del composable
LaunchedEffect(key) { fetchData() }

Descomposición Paralela

Usa coroutineScope + async para trabajo en paralelo:

suspend fun loadDashboard(): Dashboard = coroutineScope {
    val items = async { itemRepository.getRecent() }
    val stats = async { statsRepository.getToday() }
    val profile = async { userRepository.getCurrent() }
    Dashboard(
        items = items.await(),
        stats = stats.await(),
        profile = profile.await()
    )
}

SupervisorScope

Usa supervisorScope cuando los fallos de un hijo no deban cancelar a los hermanos:

suspend fun syncAll() = supervisorScope {
    launch { syncItems() }       // el fallo aquí no cancelará syncStats
    launch { syncStats() }
    launch { syncSettings() }
}

Patrones de Flow

Flow Frío — Conversión de Llamada Única a Flujo Continuo

fun observeItems(): Flow<List<Item>> = flow {
    // Se reemite cada vez que la base de datos cambia
    itemDao.observeAll()
        .map { entities -> entities.map { it.toDomain() } }
        .collect { emit(it) }
}

StateFlow para el Estado de la UI

class DashboardViewModel(
    observeProgress: ObserveUserProgressUseCase
) : ViewModel() {
    val progress: StateFlow<UserProgress> = observeProgress()
        .stateIn(
            scope = viewModelScope,
            started = SharingStarted.WhileSubscribed(5_000),
            initialValue = UserProgress.EMPTY
        )
}

WhileSubscribed(5_000) mantiene activo el flujo ascendente durante 5 segundos después de que el último suscriptor desaparece — sobrevive a cambios de configuración sin reiniciar.

Combinación de Varios Flows

val uiState: StateFlow<HomeState> = combine(
    itemRepository.observeItems(),
    settingsRepository.observeTheme(),
    userRepository.observeProfile()
) { items, theme, profile ->
    HomeState(items = items, theme = theme, profile = profile)
}.stateIn(viewModelScope, SharingStarted.WhileSubscribed(5_000), HomeState())

Operadores de Flow

// Debounce en la entrada de búsqueda
searchQuery
    .debounce(300)
    .distinctUntilChanged()
    .flatMapLatest { query -> repository.search(query) }
    .catch { emit(emptyList()) }
    .collect { results -> _state.update { it.copy(results = results) } }

// Reintento con backoff exponencial
fun fetchWithRetry(): Flow<Data> = flow { emit(api.fetch()) }
    .retryWhen { cause, attempt ->
        if (cause is IOException && attempt < 3) {
            delay(1000L * (1 shl attempt.toInt()))
            true
        } else {
            false
        }
    }

SharedFlow para Eventos Únicos

class ItemListViewModel : ViewModel() {
    private val _effects = MutableSharedFlow<Effect>()
    val effects: SharedFlow<Effect> = _effects.asSharedFlow()

    sealed interface Effect {
        data class ShowSnackbar(val message: String) : Effect
        data class NavigateTo(val route: String) : Effect
    }

    private fun deleteItem(id: String) {
        viewModelScope.launch {
            repository.delete(id)
            _effects.emit(Effect.ShowSnackbar("Ítem eliminado"))
        }
    }
}

// Recoger en el Composable
LaunchedEffect(Unit) {
    viewModel.effects.collect { effect ->
        when (effect) {
            is Effect.ShowSnackbar -> snackbarHostState.showSnackbar(effect.message)
            is Effect.NavigateTo -> navController.navigate(effect.route)
        }
    }
}

Dispatchers

// Trabajo intensivo de CPU
withContext(Dispatchers.Default) { parseJson(largePayload) }

// Trabajo de E/S
withContext(Dispatchers.IO) { database.query() }

// Hilo principal (UI) — predeterminado en viewModelScope
withContext(Dispatchers.Main) { updateUi() }

En KMP, usa Dispatchers.Default y Dispatchers.Main (disponibles en todas las plataformas). Dispatchers.IO es solo para JVM/Android — usa Dispatchers.Default en otras plataformas o proporciona mediante DI.

Cancelación

Cancelación Cooperativa

Los bucles largos deben verificar la cancelación:

suspend fun processItems(items: List<Item>) = coroutineScope {
    for (item in items) {
        ensureActive()  // lanza CancellationException si se cancela
        process(item)
    }
}

Limpieza con try/finally

viewModelScope.launch {
    try {
        _state.update { it.copy(isLoading = true) }
        val data = repository.fetch()
        _state.update { it.copy(data = data) }
    } finally {
        _state.update { it.copy(isLoading = false) }  // siempre se ejecuta, incluso con cancelación
    }
}

Pruebas

Pruebas de StateFlow con Turbine

@Test
fun `la búsqueda actualiza la lista de ítems`() = runTest {
    val fakeRepository = FakeItemRepository().apply { emit(testItems) }
    val viewModel = ItemListViewModel(GetItemsUseCase(fakeRepository))

    viewModel.state.test {
        assertEquals(ItemListState(), awaitItem())  // estado inicial

        viewModel.onSearch("consulta")
        val loading = awaitItem()
        assertTrue(loading.isLoading)

        val loaded = awaitItem()
        assertFalse(loaded.isLoading)
        assertEquals(1, loaded.items.size)
    }
}

Pruebas con TestDispatcher

@Test
fun `la carga paralela se completa correctamente`() = runTest {
    val viewModel = DashboardViewModel(
        itemRepo = FakeItemRepo(),
        statsRepo = FakeStatsRepo()
    )

    viewModel.load()
    advanceUntilIdle()

    val state = viewModel.state.value
    assertNotNull(state.items)
    assertNotNull(state.stats)
}

Faking Flows

class FakeItemRepository : ItemRepository {
    private val _items = MutableStateFlow<List<Item>>(emptyList())

    override fun observeItems(): Flow<List<Item>> = _items

    fun emit(items: List<Item>) { _items.value = items }

    override suspend fun getItemsByCategory(category: String): Result<List<Item>> {
        return Result.success(_items.value.filter { it.category == category })
    }
}

Anti-patrones a Evitar

  • Usar GlobalScope — filtra coroutines, sin cancelación estructurada
  • Recoger Flows en init {} sin un ámbito — usa viewModelScope.launch
  • Usar MutableStateFlow con colecciones mutables — usa siempre copias inmutables: _state.update { it.copy(list = it.list + newItem) }
  • Capturar CancellationException — déjala propagarse para una cancelación correcta
  • Usar flowOn(Dispatchers.Main) para recoger — el dispatcher de recolección es el del llamador
  • Crear Flow en @Composable sin remember — recrea el flujo en cada recomposición

Referencias

Consulta el skill: compose-multiplatform-patterns para el consumo de Flows en la UI. Consulta el skill: android-clean-architecture para saber dónde encajan las coroutines en las capas.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

accessibility

Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA. Use when building or auditing UI that must meet WCAG 2.2 Level AA, or when reviewing a change for keyboard, contrast, or screen-reader support.

affaan-m/claude-api

Anthropic Claude API patterns for Python and TypeScript. Covers Messages API, streaming, tool use, vision, extended thinking, batches, prompt caching, and Claude Agent SDK. Use when building applications with the Claude API or Anthropic SDKs.

affaan-m/everything-claude-code

End-to-end marketing campaign planning and execution. Covers audience research, positioning, campaign angle definition, landing page copy, email sequences, social posts, ad copy, short-form video scripts, and content calendars. Use as the orchestration layer for multi-channel product launches. Use when planning or executing a multi-channel product launch, or producing landing page, email, social, or ad copy.

affaan-m/everything-claude-code

Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

affaan-m/everything-claude-code-conventions

Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

affaan-m/frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build web components, pages, or applications and the visual direction matters as much as the code quality.

affaan-m/gget

gget CLI and Python workflow for quick genomic database queries, sequence lookup, BLAST-style searches, enrichment checks, and reproducible bioinformatics evidence logs.

affaan-m/literature-review

Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.

affaan-m/motion-ui

Production-ready UI motion system for React/Next.js. Use when implementing animations, transitions, or motion patterns.

affaan-m/project-guidelines-example

Example project-specific skill template based on a real production application.

affaan-m/pubmed-database

Direct PubMed and NCBI E-utilities search workflows for biomedical literature, MeSH queries, PMID lookup, citation retrieval, and API-backed literature monitoring.

affaan-m/scholar-evaluation

Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.

affaan-m/uspto-database

USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.

agent-architecture-audit

Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first fixes. Essential for developers building agent applications, autonomous loops, or any LLM-powered feature. Use when an agent or LLM feature misbehaves and the failing layer is unknown, or before shipping an agent stack.

agent-eval

Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics. Use when choosing between coding agents, or when a change to an agent setup needs measured pass rate, cost, and time rather than an impression.

agent-harness-construction

Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates. Use when defining or revising an agent

agentic-engineering

Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing. Use when planning or executing engineering work that agents will carry out end to end.

agentic-os

Build persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases. Use when building a persistent multi-agent system on Claude Code with its own memory, commands, and scheduling.

agent-introspection-debugging

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.

agent-payment-x402

Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk and X Layer through OKX Payments / OKX Agent Payments Protocol. Use when an agent must pay for something itself and needs per-task budgets, spending controls, and a non-custodial wallet.

Skills relacionados