🌊
QualityShell

Collecting Flows Safely

by skydoves

Collecting Flows Safely is a Quality skill for Claude Code, published by skydoves in compose-performance-skills.

492 stars17 forkson skydoves/compose-performance-skillsAdded 2026/08/26+1% in starsRepository updated 2026/06/16
agent-skillsandroidclaudeclaude-codecomposecompose-performancejetpack-composekotlinllm-toolsrecompositionskydoves
Install in seconds
Install Collecting Flows Safely
Copy Collecting Flows Safely into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/skydoves/compose-performance-skills/tree/main/side-effects/collecting-flows-safely ~/.claude/skills/collecting-flows-safely

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/skydoves/compose-performance-skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
side-effects/collecting-flows-safely/SKILL.md in skydoves/compose-performance-skills
Installs to
~/.claude/skills/collecting-flows-safely
Collection
One of 25 skills cataloged from this repository
Category
Quality1354 skills

What Collecting Flows Safely does

Collecting Flows Safely helps migrate Compose screens from collectAsState() to collectAsStateWithLifecycle() and tame high-frequency flows with conflate(), distinctUntilChanged(), and snapshotFlow. Use it when background collection, unstable Flow parameters, or chatty streams are causing wasted work or extra recompositions.

Collecting Flows Safely is cataloged under Quality on DirSkills. Collecting Flows Safely comes from a repository tagged agent-skills, android, claude, claude-code and compose.

Documentation

README

Collecting Flows Safely — keep upstream work tied to the UI lifecycle

collectAsState() keeps collecting whenever the composable is in composition, including while the app is backgrounded — that wastes CPU and battery. collectAsStateWithLifecycle() ties collection to a Lifecycle.State (default STARTED) so backgrounding pauses upstream work. For chatty flows, pair the consumer with .conflate() and .distinctUntilChanged() so Compose only sees meaningful changes. Skydoves hot take #4: a Flow<T> parameter on a composable is unstable and blocks skipping for the whole composable — collect at the caller and pass the resolved value.

When to use this skill

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Collecting Flows Safely

  • What else does skydoves publish alongside Collecting Flows Safely?

    Collecting Flows Safely is one of 25 skills that DirSkills catalogs from skydoves/compose-performance-skills, the repository it ships in. Its siblings there include Auditing Compose Performance, Avoiding Subcomposition Pitfalls and Choosing DerivedStateOf. Each one is a separate skill with its own page in this directory, installs the same way Collecting Flows Safely does, and is maintained by skydoves in that same repository. The rest of the collection is listed on the skydoves/compose-performance-skills page.

  • How does Collecting Flows Safely compare to other Quality skills?

    Collecting Flows Safely ranks #1221 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Collecting Flows Safely against them. Open each page to compare what they document and how they install.

More from skydoves/compose-performance-skills

Collecting Flows Safely is one of 25 skills cataloged on DirSkills from skydoves/compose-performance-skills.

See all 25 skills
🔍
5d ago

Auditing Compose Performance

Auditing Compose Performance runs a Measure → Diagnose → Fix → Verify workflow for broad Jetpack Compose slowdowns. Use it for perf audits, sprint kickoffs, and written reports when you need baseline metrics, causes, fixes, and verification.
Quality
49217
🧩
5d ago

Avoiding Subcomposition Pitfalls

Avoiding Subcomposition Pitfalls explains when SubcomposeLayout, BoxWithConstraints, or Scaffold cause repeated measure-phase composition in Jetpack Compose. Use it to replace unnecessary subcomposition with cheaper layout primitives or tune it when subcomposition is required.
Frontend
49217
🧩
5d ago

Choosing DerivedStateOf

Choosing DerivedStateOf helps decide when Jetpack Compose derivedStateOf reduces recompositions and when it is just overhead. It covers input-vs-output frequency, required remember wrapping, stale captures, and snapshotFlow for one-shot side effects.
Frontend
49217
📜
5d ago

Configuring Lazy Prefetch

Configuring Lazy Prefetch tunes Jetpack Compose lazy-layout cache windows and nested prefetch for heavy scrolling. Use it when dropped frames come from composition work, especially with LazyLayoutCacheWindow or inner lazy layouts.
Frontend
49217
🛠️
5d ago

Configuring R8 For Compose

Configuring R8 For Compose explains how to set up minification for a Jetpack Compose app with R8 full mode, resource shrinking, and minimal keep rules. Use it when enabling release shrinking, fixing missing keeps, or checking why Compose does not need blanket keep rules.
DevOps
49217
🔍
5d ago

Debugging Recompositions

Debugging Recompositions finds which Jetpack Compose composables are recomposing and why using Layout Inspector counts, skip counts, and argument change reasons. It also covers runtime @TraceRecomposition checks to confirm fixes in release-like builds.
Quality
49217