compose-coroutines

A set of rules for handling scrolling and coroutines in Jetpack Compose, Android's interface toolkit. It covers automatic scrolling, detecting user scrolling, and safely resetting state when work is cancelled.

In plain words
What is it for?
Use it when building Compose screens with auto-scroll, animated scrolling, or coroutine-based scroll detection.
Why use it?
It prevents automatic scrolling from being mistaken for a user's gesture and avoids state flags getting stuck after cancellation.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/baijum/ukulele-companion/compose-coroutines
Clone the repo
git clone --depth 1 https://github.com/baijum/ukulele-companion

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 543 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00543
Opus 5 $0.00000 $0.00271
Sonnet 5 $0.00000 $0.00109
Haiku 4.5 $0.00000 $0.00054

Measured yesterday against content hash 335dfdb3112f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

compose-coroutines scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/compose-coroutines.mdc · 68 lines

What it actually says

  • Guard programmatic scroll from state observers

    scrollState.isScrollInProgress cannot distinguish between a user finger drag and a programmatic animateScrollTo call. If you observe isScrollInProgress to detect manual scrolling, always gate it with a flag:

    val programmaticScroll = remember { mutableStateOf(false) }
    
    // Auto-scroll loop
    LaunchedEffect(autoScrolling) {
        if (autoScrolling) {
            while (autoScrolling) {
                programmaticScroll.value = true
                try {
                    scrollState.animateScrollTo(/* ... */)
                } finally {
                    programmaticScroll.value = false
                }
                delay(16L)
            }
        }
    }
    
    // Manual-scroll detector — skip when programmatic
    LaunchedEffect(scrollState.isScrollInProgress) {
        if (scrollState.isScrollInProgress && autoScrolling && !programmaticScroll.value) {
            autoScrolling = false
        }
    }
    
  • Always wrap cancellable suspend calls in try/finally

    animateScrollTo, animateTo, and similar Compose suspend functions are cancellable. If you set a flag before calling them, reset it in a finally block so the flag is cleared even if the coroutine is cancelled (e.g., by user touch or LaunchedEffect recomposition):

    // ✅ DO
    flag.value = true
    try {
        scrollState.animateScrollTo(target)
    } finally {
        flag.value = false
    }
    
    // ❌ DON'T — flag stays true if animateScrollTo is cancelled
    flag.value = true
    scrollState.animateScrollTo(target)
    flag.value = false
    
  • Prefer snapshotFlow over LaunchedEffect(stateValue) for contextual reactions

    LaunchedEffect(stateValue) restarts whenever stateValue changes, but you lose the previous value. When you need to compare old vs. new, or combine the state change with other conditions, use snapshotFlow:

    // ✅ Richer context — can debounce, filter, combine
    LaunchedEffect(Unit) {
        snapshotFlow { scrollState.isScrollInProgress }
            .filter { it && !programmaticScroll.value }
            .collect { autoScrolling = false }
    }
    
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 68 lines · 0 tokens per session scan A 335dfdb3112f

Subscribe to this mod's changes

compose-coroutines is a cursor rule published in the GitHub repository baijum/ukulele-companion (13 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 543 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.