Communitygithub.com

Kotlin Coroutines e Flows

Padrões de Kotlin Coroutines e Flow para Android e KMP — concorrência estruturada, operadores Flow, StateFlow, tratamento de erros e testes. Use ao escrever código com coroutines ou Flow em Android ou KMP, ou ao depurar cancelamento e concorrência.

O que é Kotlin Coroutines e Flows?

Este skill fornece padrões e boas práticas para usar Kotlin Coroutines e Flow em projetos Android e Kotlin Multiplatform (KMP). Ele cobre desde conceitos fundamentais de concorrência estruturada (hierarquia de escopos, decomposição paralela com `coroutineScope`/`async` e `supervisorScope`) até padrões de Flow para estados reativos, como StateFlow para UI, SharedFlow para eventos únicos, combinação de múltiplos Fluxos e operadores como `debounce`, `distinctUntilChanged` e `flatMapLatest`. Também inclui orientações sobre uso correto de `Dispatchers` (Default, IO, Main) em diferentes plataformas, técnicas de cancelamento cooperativo (com `ensureActive()` e `try/finally`), e estratégias de teste usando Turbine e `TestDispatcher`. O skill é ativado sempre que você escrever código assíncrono com coroutines, usar Flow para dados reativos ou precisar testar coroutines e Flows, ajudando a evitar anti-padrões como `GlobalScope`, coleta de Flow sem escopo adequado e captura inadequada de `CancellationException`. Ideal para desenvolvedores Android e KMP que desejam escrever código conciso, seguro e de fácil manutenção com coroutines e Fluxos.

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

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

O que Kotlin Coroutines e Flows faz?

Padrões para concorrência estruturada, streams reativos baseados em Flow e testes de coroutines em projetos Android e Kotlin Multiplatform.

Quando Ativar

  • Escrever código assíncrono com Kotlin coroutines
  • Usar Flow, StateFlow ou SharedFlow para dados reativos
  • Lidar com operações concorrentes (carregamento paralelo, debounce, retry)
  • Testar coroutines e Flows
  • Gerenciar escopos de coroutine e cancelamento

Concorrência Estruturada

Hierarquia de Escopos

Application
  └── viewModelScope (ViewModel)
        └── coroutineScope { } (filho estruturado)
              ├── async { } (tarefa concorrente)
              └── async { } (tarefa concorrente)

Sempre use concorrência estruturada — nunca GlobalScope:

// RUIM
GlobalScope.launch { fetchData() }

// BOM — escopo ao ciclo de vida da ViewModel
viewModelScope.launch { fetchData() }

// BOM — escopo ao ciclo de vida do composable
LaunchedEffect(key) { fetchData() }

Decomposição Paralela

Use coroutineScope + async para trabalho 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

Use supervisorScope quando a falha de um filho não deve cancelar os irmãos:

suspend fun syncAll() = supervisorScope {
    launch { syncItems() }       // falha aqui não cancelará syncStats
    launch { syncStats() }
    launch { syncSettings() }
}

Padrões de Flow

Flow Frio — Conversão de Evento Único para Stream

fun observeItems(): Flow<List<Item>> = flow {
    // Reemite sempre que o banco de dados mudar
    itemDao.observeAll()
        .map { entities -> entities.map { it.toDomain() } }
        .collect { emit(it) }
}

StateFlow para Estado da 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) mantém o upstream ativo por 5 segundos após o último assinante sair — sobrevive a mudanças de configuração sem reiniciar.

Combinando Múltiplos 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 Flow

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

// Retry com 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("Item deletado"))
        }
    }
}

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

Dispatchers

// Trabalho intensivo em CPU
withContext(Dispatchers.Default) { parseJson(largePayload) }

// Trabalho de I/O
withContext(Dispatchers.IO) { database.query() }

// Thread principal (UI) — padrão em viewModelScope
withContext(Dispatchers.Main) { updateUi() }

No KMP, use Dispatchers.Default e Dispatchers.Main (disponível em todas as plataformas). Dispatchers.IO é apenas JVM/Android — use Dispatchers.Default em outras plataformas ou forneça via DI.

Cancelamento

Cancelamento Cooperativo

Loops longos devem verificar cancelamento:

suspend fun processItems(items: List<Item>) = coroutineScope {
    for (item in items) {
        ensureActive()  // lança CancellationException se cancelado
        process(item)
    }
}

Limpeza com 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) }  // sempre executa, mesmo com cancelamento
    }
}

Testes

Testando StateFlow com Turbine

@Test
fun `pesquisa atualiza lista de itens`() = runTest {
    val fakeRepository = FakeItemRepository().apply { emit(testItems) }
    val viewModel = ItemListViewModel(GetItemsUseCase(fakeRepository))

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

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

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

Testando com TestDispatcher

@Test
fun `carregamento paralelo completa corretamente`() = runTest {
    val viewModel = DashboardViewModel(
        itemRepo = FakeItemRepo(),
        statsRepo = FakeStatsRepo()
    )

    viewModel.load()
    advanceUntilIdle()

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

Simulando 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-Padrões a Evitar

  • Usar GlobalScope — vaza coroutines, sem cancelamento estruturado
  • Coletar Flows em init {} sem um escopo — use viewModelScope.launch
  • Usar MutableStateFlow com coleções mutáveis — sempre use cópias imutáveis: _state.update { it.copy(list = it.list + newItem) }
  • Capturar CancellationException — deixe-o propagar para cancelamento adequado
  • Usar flowOn(Dispatchers.Main) para coletar — o dispatcher de coleta é o dispatcher do chamador
  • Criar Flow dentro de @Composable sem remember — recria o flow a cada recomposição

Referências

Veja skill: compose-multiplatform-patterns para consumo de Flows na UI. Veja skill: android-clean-architecture para onde as coroutines se encaixam nas camadas.

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.

Habilidades Relacionadas