Communitygithub.com

kotlin-coroutines-flows

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

¿Qué es kotlin-coroutines-flows?

Este skill proporciona patrones y mejores prácticas para trabajar con coroutines y Flows en Kotlin, tanto para Android como para Kotlin Multiplatform (KMP). Está diseñado para desarrolladores que necesitan gestionar concurrencia de manera estructurada, evitando errores comunes como el uso de GlobalScope o la cancelación incorrecta de coroutines. Incluye ejemplos detallados de cómo usar StateFlow para el estado de la UI, SharedFlow para eventos únicos, y operadores como debounce, distinctUntilChanged y flatMapLatest para transformar flujos de datos reactivos. También cubre la combinación de múltiples Flows con combine, la gestión de dispatchers (Default, IO, Main) en diferentes plataformas, y estrategias de reintento con backoff exponencial. Para pruebas, el skill recomienda usar la biblioteca Turbine para verificar emisiones de StateFlow y TestDispatcher para controlar el tiempo en pruebas de coroutines. Es compatible con Android, KMP y entornos de servidor Kotlin, y se activa automáticamente cuando se escribe código asíncrono con coroutines o se implementan Flows para reactividad.

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

Preguntar en tu IA favorita

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

Documentación

Corutinas y Flujos de Kotlin (Kotlin Coroutines & Flows)

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

Cuándo activarlo

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

Concurrencia estructurada

Jerarquía de ámbitos

Aplicación
  └── viewModelScope (ViewModel)
        └── coroutineScope { } (hijo estructurado)
              ├── async { } (tarea concurrente)
              └── async { } (tarea concurrente)

Siempre usa 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 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 el fallo de un hijo no deba cancelar a los hermanos:

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

Patrones de Flow

Flow frío (Cold Flow) — Conversión de disparo único 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 origen ascendente durante 5 segundos después de que el último suscriptor se vaya — sobrevive a cambios de configuración sin reiniciar.

Combinar múltiples 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 para entrada de búsqueda
searchQuery
    .debounce(300)
    .distinctUntilChanged()
    .flatMapLatest { query -> repository.search(query) }
    .catch { emit(emptyList()) }
    .collect { results -> _state.update { it.copy(results = results) } }

// Reintentos con retroceso 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 de una sola vez

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("Elemento eliminado"))
        }
    }
}

// Recolectar en un 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 ligado a E/S
withContext(Dispatchers.IO) { database.query() }

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

En KMP, usa Dispatchers.Default y Dispatchers.Main (disponibles en todas las plataformas). Dispatchers.IO es solo JVM/Android — usa Dispatchers.Default en otras plataformas o provee 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 está cancelado
        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 en cancelación
    }
}

Pruebas

Probar StateFlow con Turbine

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

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

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

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

Probar 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)
}

Simular Flows (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 })
    }
}

Antipatrones a evitar

  • Usar GlobalScope — fuga de corutinas, sin cancelación estructurada
  • Recolectar 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 propagar para una cancelación adecuada
  • Usar flowOn(Dispatchers.Main) para recolectar — el dispatcher de recolección es el del llamador
  • Crear Flow en un @Composable sin remember — recrea el flujo en cada recomposición

Referencias

Consulta la habilidad: compose-multiplatform-patterns para el consumo de Flows en la UI. Consulta la habilidad: android-clean-architecture para saber dónde encajan las corutinas 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/content-engine

Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.

affaan-m/ECC

Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.

affaan-m/fal-ai-media

Unified media generation via fal.ai MCP — image, video, and audio. Covers text-to-image (Nano Banana), text/image-to-video (Seedance, Kling, Veo 3), text-to-speech (CSM-1B), and video-to-audio (ThinkSound). Use when the user wants to generate images, videos, or audio with AI.

affaan-m/manim-video

日本語翻訳:このファイルは manim-video 用の日本語翻訳が必要です

affaan-m/remotion-video-creation

Remotion のベストプラクティス - React で動画を作成する。3D、アニメーション、音声、字幕、チャート、トランジションなどをカバーするドメイン固有の29のルール。

affaan-m/video-editing

AI-assisted video editing workflows for cutting, structuring, and augmenting real footage. Covers the full pipeline from raw capture through FFmpeg, Remotion, ElevenLabs, fal.ai, and final polish in Descript or CapCut. Use when the user wants to edit video, cut footage, create vlogs, or build video content.

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.

agent-self-evaluation

Use after completing any non-trivial task. The agent self-rates its output on 5 axes — accuracy, completeness, clarity, actionability, conciseness — with concrete evidence per criterion. Produces a structured 1-5 scorecard with specific improvement suggestions.

agent-sort

Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

ai-first-engineering

Engineering operating model for teams where AI agents generate a large share of implementation output. Use when setting team process, review gates, or ownership rules for a codebase largely written by agents.

ai-regression-testing

Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code. Use when adding regression coverage to AI-assisted code, or when the same model both wrote and reviewed a change.

android-clean-architecture

Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns. Use when structuring modules, layers, or data flow in an Android or KMP project.

angular-developer

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.

Skills relacionados