agentleFS
Sign inStart free
krutikJainkrutikJain/android-agent-skills/.github/skills/android-compose-state-effects/SKILL.md

android-compose-state-effects

Skill14 starsChanged 8 months agoMITView on GitHub

Manage Compose state, remember APIs, side effects, snapshots, and lifecycle-aware collection without leaks or loops.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the request is about: compose side effect problem, remember vs derivedstateof, collect flow in compose screen.

    line 17
  2. Distinctive:

    Keep durable UI state separate from transient events such as snackbars, navigation, and analytics.

    line 28
  3. Very specific:

    Prefer lifecycle-aware collection such as collectAsStateWithLifecycle for UI-facing flows.

    line 33
  4. Very specific:

    Use rememberUpdatedState when an effect should see the latest lambda or value without restarting.

    line 34
  5. Distinctive:

    Keep one-shot effects out of immutable screen state when they are really events.

    line 35
  6. Distinctive:

    Do not launch coroutines or trigger navigation directly from the composable body outside the appropriate effect APIs.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Android Compose State Effects

When To Use

  • Use this skill when the request is about: compose side effect problem, remember vs derivedstateof, collect flow in compose screen.
  • Primary outcome: Manage Compose state, remember APIs, side effects, snapshots, and lifecycle-aware collection without leaks or loops.
  • Reach for this skill when the problem lives inside a composable or Compose runtime primitive, not when redesigning app-wide state holders or reducers.
  • This skill is about runtime primitives inside Compose. If the question is reducer design, screen contracts, or ViewModel ownership, hand off to android-state-management.
  • Handoff skills when the scope expands:
  • android-state-management
  • android-compose-performance

Workflow

  1. Classify the issue first: local remembered state, saved state, derived state, lifecycle-aware collection, or one-off side effects.
  2. Pick the narrowest Compose primitive that matches that problem: remember, rememberSaveable, derivedStateOf, produceState, collectAsStateWithLifecycle, LaunchedEffect, DisposableEffect, SideEffect, or snapshotFlow.
  3. Keep durable UI state separate from transient events such as snackbars, navigation, and analytics.
  4. Stabilize effect keys and callback references so recomposition does not relaunch work or capture stale lambdas.
  5. Hand off broader state-holder design to android-state-management only after the Compose-runtime issue is isolated.

Guardrails

  • Prefer lifecycle-aware collection such as collectAsStateWithLifecycle for UI-facing flows.
  • Use rememberUpdatedState when an effect should see the latest lambda or value without restarting.
  • Keep one-shot effects out of immutable screen state when they are really events.
  • Do not launch coroutines or trigger navigation directly from the composable body outside the appropriate effect APIs.

Anti-Patterns

  • Using LaunchedEffect(Unit) or unstable keys when the effect should restart on real dependency changes.
  • Collecting flows in multiple places and wondering why events duplicate.
  • Storing transient events as persistent booleans in screen state and then manually resetting them.
  • Using derivedStateOf or snapshotFlow when plain state reads would be simpler and cheaper.

Review Focus

  • Which runtime primitive owns this behavior?
  • Are recomposition and effect restarts intentional?
  • Are state and event channels modeled separately?
  • Is collection lifecycle-aware and cancellation-safe?

Examples

Happy path

  • Scenario: Collect task state and snackbar events in Compose without duplicate launches.
  • Command: cd examples/orbittasks-compose && ./gradlew :app:testDebugUnitTest

Edge case

  • Scenario: Handle recomposition when permission state and sync state change together.
  • Command: cd examples/orbittasks-compose && ./gradlew :app:assembleDebug

Failure recovery

  • Scenario: Disambiguate state/effects work from generic Compose layout or state-management requests.
  • Command: python3 scripts/eval_triggers.py --skill android-compose-state-effects

Done Checklist

  • The chosen Compose primitive matches the actual runtime problem.
  • Effects have stable keys and do not duplicate on recomposition.
  • State and events are separated clearly.
  • Broader app-state architecture work is handed off instead of mixed into the composable fix.

Official References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free