Agent Skills › chrisbanes/skills › kotlin-concurrency-and-flow

kotlin-concurrency-and-flow

GitHub

规范 Kotlin 协程作用域、生命周期及 Flow 状态事件模型，确保异步工作拥有明确的所有权和取消边界，指导代码编写与审查。

skills/kotlin-concurrency-and-flow/SKILL.md chrisbanes/skills

Trigger Scenarios

编写或审查 Kotlin 协程相关代码涉及 StateFlow、SharedFlow、Channel 的状态管理处理 CoroutineScope 所有权和取消逻辑

Install

npx skills add chrisbanes/skills --skill kotlin-concurrency-and-flow -g -y

More Options

Use without installing

npx skills use chrisbanes/skills@kotlin-concurrency-and-flow

指定 Agent (Claude Code)

npx skills add chrisbanes/skills --skill kotlin-concurrency-and-flow -a claude-code -g -y

安装 repo 全部 skill

npx skills add chrisbanes/skills --all -g -y

预览 repo 内 skill

npx skills add chrisbanes/skills --list

SKILL.md

Frontmatter

{
    "name": "kotlin-concurrency-and-flow",
    "description": "Use when writing or reviewing Kotlin coroutine scope ownership, init launches, non-suspending launch APIs, runBlocking, cancellation, StateFlow, SharedFlow, Channel, stateIn, SharingStarted, state updates, or one-shot events."
}

Kotlin concurrency and Flow

Core principle

Give asynchronous work an explicit owner and lifetime, then model durable state and transient events with primitives whose delivery and replay semantics match the product contract.

Procedure

Identify each coroutine owner, cancellation boundary, producer, consumer, durable state, and transient event.
Before changing an API, compare its existing caller-visible contract with the required owner and lifetime. If a suspend API already gives its caller cancellation, result, and failure ownership, finish with no change; do not add a scope, launch, callback, or deferred wrapper merely for convenience.
Select a scope whose lifecycle owns the work; do not retain arbitrary scopes or hide unstructured launches behind non-suspending APIs.
Model renderable, current data as state and imperative one-shot work as an event only when its loss and replay behavior are explicitly acceptable.
Choose Flow sharing and buffering semantics from the producer and consumer lifetimes rather than from a default.
Read the focused reference for the material concern below.
Finish when cancellation, restart, replay, and failure behavior are all observable from the public API and no caller must guess who owns the work.

Topic router

Signal	Read
Stored `CoroutineScope`, `init { launch }`, fire-and-forget API, `runBlocking`, broad catch, or cancellation boundary	Structured concurrency
`StateFlow`, `SharedFlow`, `Channel`, `stateIn`, `SharingStarted`, `.value`, state updates, sentinel values, or one-shot events	Flow state and events
Compose collection or UI effect handling	Compose state and effects