hamen/compose_skill

{   "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",

"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",

"source": {         "source": "git-subdir",         "url": "https://github.com/hamen/compose_skill.git",

"source": "git-subdir",         "url": "https://github.com/hamen/compose_skill.git",         "path": "skills/compose-agent"

"url": "https://github.com/hamen/compose_skill.git",

"source": {         "source": "git-subdir",         "url": "https://github.com/hamen/compose_skill.git",

"source": "git-subdir",         "url": "https://github.com/hamen/compose_skill.git",         "path": "skills/jetpack-compose-audit"

"url": "https://github.com/hamen/compose_skill.git",

#!/usr/bin/env bash

!/static splash icon may render blurry/i.test(auditDocs) ||   !/non-scored|not score/i.test(auditDocs) ||   !auditDocs.includes('https://issuetracker.google.com/issues/520672537')

!/non-scored|not score/i.test(auditDocs) ||   !auditDocs.includes('https://issuetracker.google.com/issues/520672537') ) {

!auditDocs.includes('https://issuetracker.google.com/issues/520672537')

throw new Error(`${evalFile} eval ${item.id} is missing a non-empty "${field}"`);

throw new Error(`${evalFile} eval ${item.id} must have a "files" array`);

throw new Error(`${evalFile} eval ${item.id} must have a non-empty "expectations" array`);

throw new Error(`${evalFile} eval ${item.id} expectations must all be non-empty strings`);

"name": "Ivan Morgillo"   },   "repository": "https://github.com/hamen/compose_skill",

},   "repository": "https://github.com/hamen/compose_skill",   "license": "MIT",

"repository": "https://github.com/hamen/compose_skill",

"name": "Ivan Morgillo"   },   "repository": "https://github.com/hamen/compose_skill",

},   "repository": "https://github.com/hamen/compose_skill",   "license": "MIT",

"repository": "https://github.com/hamen/compose_skill",

Read, Glob, Grep, Edit, Write, Bash

<https://developer.android.com/topic/architecture/ui-layer/state-production#continuous-vs-discrete>

<https://developer.android.com/develop/ui/compose/api-guidelines#naming-modifiers>

<https://developer.android.com/develop/ui/compose/performance/bestpractices#defer-reads-as-long-as-possible>

- `https://developer.android.com/develop/ui/compose` and its subpages

- `https://developer.android.com/kotlin/style-guide`

- `https://kotlinlang.org/docs/coding-conventions.html`

- `https://www.jetbrains.com/help/kotlin-multiplatform-dev/`

- `https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-api-guidelines.md`

- `https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-component-api-guidelines.md`

<https://developer.android.com/develop/ui/compose/animation/choose-api>

<https://developer.android.com/develop/ui/compose/animation/value-based#animatable>

<https://developer.android.com/develop/ui/compose/animation/value-based#animatable>

<https://developer.android.com/develop/ui/compose/animation/value-based#updatetransition>

<https://developer.android.com/develop/ui/compose/animation/customize#animationspec>

<https://developer.android.com/develop/ui/compose/tooling/animation-preview>

<https://developer.android.com/develop/ui/compose/performance/bestpractices#defer-reads>

<https://developer.android.com/develop/ui/compose/animation/composables-modifiers#animatedcontent>

<https://developer.android.com/develop/ui/compose/animation/composables-modifiers#animatedvisibility>

<https://developer.android.com/develop/ui/compose/animation/composables-modifiers#animatedcontentsize>

<https://developer.android.com/develop/ui/compose/lists#item-animations>

<https://developer.android.com/develop/ui/compose/animation/value-based#rememberinfinitetransition>

<https://developer.android.com/develop/ui/compose/animation/value-based#animatable>

<https://developer.android.com/reference/kotlin/androidx/compose/ui/MotionDurationScale>

- <https://developer.android.com/develop/ui/compose/animation/choose-api>

- <https://developer.android.com/develop/ui/compose/animation/value-based>

- <https://developer.android.com/develop/ui/compose/animation/customize>

- <https://developer.android.com/develop/ui/compose/animation/composables-modifiers>

- <https://developer.android.com/develop/ui/compose/performance/bestpractices#defer-reads>

- <https://developer.android.com/develop/ui/compose/lists#item-animations>

- <https://developer.android.com/reference/kotlin/androidx/compose/ui/MotionDurationScale>

Per the AOSP source quoted in the platform issue (`https://issuetracker.google.com/issues/520672537`), there are two render paths:

<!-- res/drawable/ic_splash_logo.xml — the REAL artwork; the only copy of the paths. --> <vector xmlns:android="http://schemas.android.com/apk/res/android"

<vector xmlns:android="http://schemas.android.com/apk/res/android"

<!-- res/drawable/ic_splash.xml — what the theme points at. No animators. --> <animated-vector xmlns:android="http://schemas.android.com/apk/res/android"

<animated-vector xmlns:android="http://schemas.android.com/apk/res/android"

- `https://developer.android.com/develop/ui/compose` (canonical Compose)

- `https://developer.android.com/jetpack/androidx/releases/compose-material3` (M3 changelog)

- `https://google.github.io/accompanist/` (marks each library's migration target)

- `https://developer.android.com/develop/ui/compose/performance/bestpractices` (deferred reads)

- `https://developer.android.com/develop/ui/views/launch/splash-screen`

- `https://developer.android.com/reference/androidx/core/splashscreen/SplashScreen`

- `https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-component-api-guidelines.md`

- `https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-api-guidelines.md`

- `https://developer.android.com/develop/ui/compose/api-guidelines`

- `https://developer.android.com/develop/ui/compose/compositionlocal`

- `https://developer.android.com/topic/libraries/architecture/coroutines`

- `https://developer.android.com/topic/architecture/ui-layer/state-production`

- `https://developer.android.com/kotlin/coroutines/coroutines-best-practices`

- `https://kotlinlang.org/docs/flow.html`

- `https://developer.android.com/reference/kotlin/androidx/lifecycle/compose/package-summary` (`collectAsStateWithLifecycle`)

- `https://developer.android.com/develop/ui/compose/side-effects`

- `https://developer.android.com/develop/ui/compose/lifecycle`

- `https://developer.android.com/topic/architecture/ui-layer/state-production`

- `https://kotlinlang.org/docs/flow.html`

- `https://kotlinlang.org/api/kotlinx.coroutines/kotlinx-coroutines-core/kotlinx.coroutines.flow/-state-flow/`

- `https://kotlinlang.org/api/kotlinx.coroutines/kotlinx-coroutines-core/kotlinx.coroutines.flow/-shared-flow/`

- `https://kotlinlang.org/api/kotlinx.coroutines/kotlinx-coroutines-core/kotlinx.coroutines.flow/state-in.html`

- `https://kotlinlang.org/api/kotlinx.coroutines/kotlinx-coroutines-core/kotlinx.coroutines.flow/share-in.html`

- `https://developer.android.com/kotlin/flow`

- `https://developer.android.com/topic/architecture/ui-layer/state-production`

- `https://elizarov.medium.com/cold-flows-hot-channels-d74769805f9` (Roman Elizarov — cold flows, hot channels)

- `https://developer.android.com/develop/ui/compose/touch-input/focus`

- `https://developer.android.com/develop/ui/compose/touch-input/keyboard-input`

- `https://developer.android.com/develop/ui/compose/testing`

- `https://developer.android.com/develop/ui/compose/accessibility`

- `https://www.jetbrains.com/help/kotlin-multiplatform-dev/multiplatform-expect-actual.html`

- `https://www.jetbrains.com/help/kotlin-multiplatform-dev/compose-multiplatform.html`

- `https://developer.android.com/develop/ui/compose/migrate/multiplatform`

- `https://developer.android.com/develop/ui/compose/interop`

- `https://kotlinlang.org/docs/coding-conventions.html` — Kotlin coding conventions.

- `https://developer.android.com/kotlin/style-guide` — Android Kotlin style guide.

- `https://developer.android.com/kotlin/interop` — Kotlin ↔ Java interop rules for public APIs.

- `https://developer.android.com/develop/ui/compose/modifiers`

- `https://developer.android.com/develop/ui/compose/custom-modifiers`

- `https://developer.android.com/develop/ui/compose/graphics/draw/modifiers`

> Navigation 3 (`androidx.navigation3`) is still in **alpha** (`1.x-alpha`) — it is what Android recommends for new Compose navigation, but pin the version and expect some API churn. The shapes below are verified against the official [nav3-

<https://developer.android.com/guide/navigation/navigation-3>

- `https://developer.android.com/guide/navigation/navigation-3/basics` — Nav3 basics (`NavDisplay`, `entryProvider`, back stack as state)

- `https://developer.android.com/guide/navigation/navigation-3/save-state` — `rememberNavBackStack`, `NavKey` + `@Serializable`, the `rememberSaveableStateHolderNavEntryDecorator` / `rememberViewModelStoreNavEntryDecorator` decorators

- `https://developer.android.com/guide/navigation/navigation-3/scenes` — scene strategies (`SinglePaneSceneStrategy`, `ListDetailSceneStrategy`); they group entries by window size, they do not register deep links

- `https://developer.android.com/guide/navigation/use-graph/navigate#type-safe` — Nav2 type-safe destinations

- `https://developer.android.com/develop/ui/compose/navigation` — Compose + Nav2

- `https://github.com/android/nav3-recipes` — official Nav3 sample recipes (basic, saveable, DSL, per-entry ViewModel, list-detail scenes, results via `ResultEventBus`, deep links). The shapes in this reference are checked against these.

<https://developer.android.com/topic/libraries/architecture/paging/v3-compose>

<https://developer.android.com/topic/libraries/architecture/paging/v3-compose#collect-lazyPagingItems>

<https://developer.android.com/reference/kotlin/androidx/paging/compose/LazyPagingItems#itemKey(kotlin.Function1)>

<https://developer.android.com/reference/kotlin/androidx/paging/compose/LazyPagingItems>

- <https://developer.android.com/topic/libraries/architecture/paging/v3-compose>

- <https://developer.android.com/topic/libraries/architecture/paging/v3-overview>

- <https://developer.android.com/reference/kotlin/androidx/paging/compose/package-summary>

- <https://developer.android.com/develop/ui/compose/lists> — lazy list keys (applies to paging items)

- `https://developer.android.com/develop/ui/compose/performance/bestpractices`

- `https://developer.android.com/develop/ui/compose/performance/stability`

- `https://developer.android.com/develop/ui/compose/performance/stability/strongskipping`

- `https://developer.android.com/develop/ui/compose/performance/phases`

- `https://developer.android.com/develop/ui/compose/lists` (keys and contentType)

- `https://developer.android.com/develop/ui/compose/performance/baseline-profiles`

- `https://developer.android.com/develop/ui/compose/state`

- `https://developer.android.com/develop/ui/compose/state-hoisting`

- `https://developer.android.com/develop/ui/compose/architecture`

- `https://developer.android.com/topic/architecture/ui-layer/state-production`

- `https://developer.android.com/develop/ui/compose/state-saving`

- `https://developer.android.com/develop/ui/compose/testing`

- `https://developer.android.com/develop/ui/compose/testing/apis`

- `https://developer.android.com/develop/ui/compose/tooling/previews`

- `https://developer.android.com/develop/ui/compose/accessibility`

"name": "Ivan Morgillo"   },   "repository": "https://github.com/hamen/compose_skill",

"name": "Ivan Morgillo"   },   "repository": "https://github.com/hamen/compose_skill",

},   "repository": "https://github.com/hamen/compose_skill",   "license": "MIT",

},   "repository": "https://github.com/hamen/compose_skill",   "license": "MIT",

"repository": "https://github.com/hamen/compose_skill",

"repository": "https://github.com/hamen/compose_skill",

"name": "Ivan Morgillo"   },   "repository": "https://github.com/hamen/compose_skill",

},   "repository": "https://github.com/hamen/compose_skill",   "license": "MIT",

"repository": "https://github.com/hamen/compose_skill",

Read, Glob, Grep, Write, Bash, Agent

This skill does **not** score design or Material 3 compliance in v1. If the audit surfaces likely design-system problems, recommend a follow-up audit with the `material-3` skill (reference implementation: <https://github.com/hamen/material-

Report it as **Android Launch UX: Android 12+ static splash icon may render blurry**, not as a Compose score deduction. Evidence should include the theme item, the resolved drawable file, and whether the `res/drawable-v31` animated-vector o

- Android Developers: `Follow best practices`     `https://developer.android.com/develop/ui/compose/performance/bestpractices`

`https://developer.android.com/develop/ui/compose/performance/bestpractices`

- Android Developers: `Jetpack Compose Performance`     `https://developer.android.com/develop/ui/compose/performance` - Android Developers: `Compose phases`

`https://developer.android.com/develop/ui/compose/performance`

- Android Developers: `Compose phases`     `https://developer.android.com/develop/ui/compose/performance/phases` - Android Developers: `Stability`

`https://developer.android.com/develop/ui/compose/performance/phases`

- Android Developers: `Stability`     `https://developer.android.com/develop/ui/compose/performance/stability` - Android Developers: `Diagnose stability problems`

`https://developer.android.com/develop/ui/compose/performance/stability`

- Android Developers: `Diagnose stability problems`     `https://developer.android.com/develop/ui/compose/performance/stability/diagnose` - Android Developers: `Fix stability issues`

`https://developer.android.com/develop/ui/compose/performance/stability/diagnose`

- Android Developers: `Fix stability issues`     `https://developer.android.com/develop/ui/compose/performance/stability/fix` - Android Developers: `Strong Skipping Mode`

`https://developer.android.com/develop/ui/compose/performance/stability/fix`

- Android Developers: `Strong Skipping Mode`     `https://developer.android.com/develop/ui/compose/performance/stability/strongskipping` - Android Developers: `Performance tooling` (Compose Compiler reports / metrics)

`https://developer.android.com/develop/ui/compose/performance/stability/strongskipping`

- Android Developers: `Performance tooling` (Compose Compiler reports / metrics)     `https://developer.android.com/develop/ui/compose/performance/tooling` - Android Developers: `Baseline profiles`

`https://developer.android.com/develop/ui/compose/performance/tooling`

`https://developer.android.com/develop/ui/compose/performance/baseline-profiles`

- Android Developers: `Animations in Compose`     `https://developer.android.com/develop/ui/compose/animation/introduction`

`https://developer.android.com/develop/ui/compose/animation/introduction`

- Android Developers: `Value-based animations` (`animate*AsState`, `Animatable`, `updateTransition`, `rememberInfiniteTransition`)     `https://developer.android.com/develop/ui/compose/animation/value-based` - Android Developers: `Customize

`https://developer.android.com/develop/ui/compose/animation/value-based`

`https://developer.android.com/develop/ui/compose/animation/customize`

- Android Developers: `Paging 3 with Compose`   `https://developer.android.com/topic/libraries/architecture/paging/v3-compose`

`https://developer.android.com/topic/libraries/architecture/paging/v3-compose`

- Android Developers: `Paging 3 overview`   `https://developer.android.com/topic/libraries/architecture/paging/v3-overview` - Android Developers: `androidx.paging.compose` reference

`https://developer.android.com/topic/libraries/architecture/paging/v3-overview`

`https://developer.android.com/reference/kotlin/androidx/paging/compose/package-summary`

- Android Developers: `State and Jetpack Compose`     `https://developer.android.com/develop/ui/compose/state`

`https://developer.android.com/develop/ui/compose/state`

- Android Developers: `State hoisting`     `https://developer.android.com/develop/ui/compose/state-hoisting` - Android Developers: `Architecting your Compose UI`

`https://developer.android.com/develop/ui/compose/state-hoisting`

- Android Developers: `Architecting your Compose UI`     `https://developer.android.com/develop/ui/compose/architecture` - Android Developers: `Lists and grids` (lazy keys, `contentType`)

`https://developer.android.com/develop/ui/compose/architecture`

`https://developer.android.com/develop/ui/compose/lists`

- Android Developers: `Side-effects in Compose`\   `https://developer.android.com/develop/ui/compose/side-effects`

`https://developer.android.com/develop/ui/compose/side-effects`

`https://developer.android.com/kotlin/coroutines/coroutines-best-practices`

- Android Developers: `Style guidelines for Jetpack Compose APIs`     `https://developer.android.com/develop/ui/compose/api-guidelines`

`https://developer.android.com/develop/ui/compose/api-guidelines`

- AndroidX component guidelines: `API Guidelines for @Composable components in Jetpack Compose`     `https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-component-api-guidelines.md` - AndroidX g

`https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-component-api-guidelines.md`

- AndroidX general guidelines: `API Guidelines for Jetpack Compose`     `https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-api-guidelines.md` - Android Developers: `Custom modifiers` (`Modifie

`https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-api-guidelines.md`

- Android Developers: `Custom modifiers` (`Modifier.Node`, `composed { }` discouraged)     `https://developer.android.com/develop/ui/compose/custom-modifiers` - Android Developers: `Locally scoped data with CompositionLocal`

`https://developer.android.com/develop/ui/compose/custom-modifiers`

- Android Developers: `Locally scoped data with CompositionLocal`     `https://developer.android.com/develop/ui/compose/compositionlocal` - Android Developers: `Navigation with Compose` (Nav2)

`https://developer.android.com/develop/ui/compose/compositionlocal`

- Android Developers: `Navigation with Compose` (Nav2)   `https://developer.android.com/develop/ui/compose/navigation` - Android Developers: `Navigation 3`

`https://developer.android.com/develop/ui/compose/navigation`

- Android Developers: `Navigation 3`   `https://developer.android.com/guide/navigation/navigation-3` - nav3-recipes (official sample repo, verified API shapes)

`https://developer.android.com/guide/navigation/navigation-3`

`https://github.com/android/nav3-recipes`

- Android Developers: `Splash screens`   `https://developer.android.com/develop/ui/views/launch/splash-screen`

`https://developer.android.com/develop/ui/views/launch/splash-screen`

- AndroidX API reference: `SplashScreen`   `https://developer.android.com/reference/androidx/core/splashscreen/SplashScreen` - Android API reference: `AnimatedVectorDrawable`

`https://developer.android.com/reference/androidx/core/splashscreen/SplashScreen`

`https://developer.android.com/reference/android/graphics/drawable/AnimatedVectorDrawable`

Use the platform issue `https://issuetracker.google.com/issues/520672537` as the bug/workaround evidence for the static splash icon blur problem (it quotes the AOSP `ImmobileIconDrawable` source). Cite at least one official Android URL alon

- `https://github.com/skydoves/compose-performance`

- `https://medium.com/@idaoskooei/building-better-uis-with-jetpack-compose-best-practices-and-techniques-a1c8953bc5b8`

This skill intentionally pairs well with the `material-3` skill, which covers Material 3 design and design-system audit concerns. The reference implementation lives at `https://github.com/hamen/material-3-skill`, but recommend it by skill n

**Reference:** <https://developer.android.com/develop/ui/compose/performance/tooling>, <https://developer.android.com/develop/ui/compose/performance/stability/diagnose>

**Reference:** <https://developer.android.com/develop/ui/compose/performance/stability/fix>

**Reference:** <https://developer.android.com/develop/ui/compose/performance/baseline-profiles>, <https://developer.android.com/topic/performance/baselineprofiles/overview>

**Reference:** <https://developer.android.com/develop/ui/compose/performance> ("Run in Release Mode with R8")

**Reference:** <https://developer.android.com/develop/ui/compose/performance/stability/strongskipping>

- Evidence: `path/a.kt:42`, `path/b.kt:117`    - Fix direction: [brief recommendation]    - References: <https://developer.android.com/develop/ui/compose/performance/bestpractices>

- References: <https://developer.android.com/develop/ui/compose/performance/bestpractices>

- Finding, if risky: **Android 12+ static splash icon may render blurry** because the API 31+ resource resolves to a static `<vector>` / `<adaptive-icon>` / bitmap / layer-list instead of an `<animated-vector>` wrapper. - Fix direction: kee

- References: <https://developer.android.com/develop/ui/views/launch/splash-screen>, <https://developer.android.com/reference/androidx/core/splashscreen/SplashScreen>, <https://issuetracker.google.com/issues/520672537>

- `path/to/file1.kt:LL` — [brief reason] · References: <https://developer.android.com/...>

- `path/to/file2.kt:LL` — [brief reason] · References: <https://developer.android.com/...>

- `path/to/file1.kt:LL` — [brief reason] · References: <https://developer.android.com/...>

- `path/to/file2.kt:LL` — [brief reason] · References: <https://developer.android.com/...>

- `path/to/file1.kt:LL` — [brief reason] · References: <https://developer.android.com/...>

- `path/to/file2.kt:LL` — [brief reason] · References: <https://developer.android.com/...>

- `path/to/file1.kt:LL` — [brief reason] · References: <https://developer.android.com/...>

- `path/to/file2.kt:LL` — [brief reason] · References: <https://developer.android.com/...>

- expensive calculations cached with `remember(keys)` or moved out of composition → [docs](https://developer.android.com/develop/ui/compose/performance/bestpractices)

- stable `key =` in lazy layouts where list identity matters → [docs](https://developer.android.com/develop/ui/compose/lists)

- `contentType` on heterogeneous lazy lists, so Compose can reuse compositions only between items of the same type → [docs](https://developer.android.com/develop/ui/compose/lists)

- `derivedStateOf` used for state that changes faster than its observable output (e.g. scroll position → "show button" boolean) → [docs](https://developer.android.com/develop/ui/compose/side-effects)

- deferred reads via lambda modifiers (`Modifier.offset { … }`, `Modifier.graphicsLayer { … }`, `Modifier.drawBehind { … }`) → [docs](https://developer.android.com/develop/ui/compose/performance/bestpractices), [phases](https://developer.an

- absence of backwards writes (writing to state that has already been read in the same composition) → [docs](https://developer.android.com/develop/ui/compose/performance/bestpractices)

- absence of cross-phase back-writes — measured size/position from a layout callback consumed in layout/draw (`Modifier.layout { }` / `Modifier.drawBehind { }`) rather than round-tripped through composition-read state → [phases](https://dev

- stability hygiene: `@Stable` / `@Immutable` on data classes used as composable params → [docs](https://developer.android.com/develop/ui/compose/performance/stability)

- `kotlinx.collections.immutable` (`ImmutableList`, `PersistentList`) for collection params — earns a skip when Strong Skipping is off, and under Strong Skipping still pays off via stable `equals()` / `hashCode()` (making the instance-equal

- `compose_compiler_config.conf` used to mark third-party types stable → [fix](https://developer.android.com/develop/ui/compose/performance/stability/fix)

- typed state factories (`mutableIntStateOf`, `mutableLongStateOf`, `mutableFloatStateOf`, `mutableDoubleStateOf`) for primitives instead of boxed `mutableStateOf<Int>` → [state](https://developer.android.com/develop/ui/compose/state)

- `@ReadOnlyComposable` / `@NonRestartableComposable` used deliberately on hot-path helpers → [strong skipping](https://developer.android.com/develop/ui/compose/performance/stability/strongskipping)

- evidence of Strong Skipping Mode awareness (Kotlin 2.0.20+ / Compose Compiler 1.5.4+); opt-outs (`@NonSkippableComposable`, `@DontMemoize`) used only with justification → [strong skipping](https://developer.android.com/develop/ui/compose/

- evidence of performance-aware configuration such as baseline profiles, R8 / minify enabled in release, or `ProfileInstaller` setup → [baseline profiles](https://developer.android.com/develop/ui/compose/performance/baseline-profiles)

- `ReportDrawnWhen { ... }` used to signal first-meaningful-content for accurate TTID/TTFD metrics → [tooling](https://developer.android.com/develop/ui/compose/performance/tooling)

- edge-to-edge opt-in via `enableEdgeToEdge()` (first-party) rather than `accompanist-systemuicontroller` on projects that support it → [lists](https://developer.android.com/develop/ui/compose/lists)

- evidence the team uses Compose Compiler reports / metrics to verify skippability → [tooling](https://developer.android.com/develop/ui/compose/performance/tooling), [diagnose](https://developer.android.com/develop/ui/compose/performance/st

- animated values read through lambda modifiers (`Modifier.graphicsLayer { ... }`, `Modifier.offset { ... }`, `Modifier.drawBehind { ... }`) so per-frame updates stay in the layout/draw phase and skip recomposition → [phases](https://develo

- `Animatable` held in `remember { Animatable(...) }` and driven from a `LaunchedEffect` — state survives recomposition, animation is cancelled on dispose → [animation](https://developer.android.com/develop/ui/compose/animation/value-based)

- `AnimatedContent` used when the call site needs custom enter/exit or size-aware content transforms, while `Crossfade` is used for standard fade-only content swaps → [animation](https://developer.android.com/develop/ui/compose/animation/in

- multiple properties that animate off the same state change share one `updateTransition` instead of independent `animate*AsState` calls that can drift out of sync → [animation](https://developer.android.com/develop/ui/compose/animation/val

- non-trivial work in composable bodies — collection transforms (`filter` / `sortedBy` / `groupBy` / `sumOf`), O(N) string ops (`split`, `lines`, `lineSequence`, `replace`, `format`), `Regex(...)` constructed or executed inline, hashing or 

- lazy list items without stable keys when identity/moves matter → [lists](https://developer.android.com/develop/ui/compose/lists)

- heterogeneous lazy lists missing `contentType` → [lists](https://developer.android.com/develop/ui/compose/lists)

- reading rapidly changing state too high in the tree → [phases](https://developer.android.com/develop/ui/compose/performance/phases), [bestpractices](https://developer.android.com/develop/ui/compose/performance/bestpractices)

- frequent-state values passed to non-lambda modifiers when a layout/draw-phase alternative exists → [bestpractices](https://developer.android.com/develop/ui/compose/performance/bestpractices)

- backwards writes — writing to state already read in the same composition body → [bestpractices](https://developer.android.com/develop/ui/compose/performance/bestpractices)

- cross-phase back-writes (axis 3) — a **layout-phase** callback (`onSizeChanged` / `onGloballyPositioned` / `onPlaced`) writing state that a sibling **reads in composition** (measure → write → recompose loop). Deduct when a composition-pha

- composition-phase self-invalidation — a `SnapshotStateMap` / `SnapshotStateList` mutated (`putAll` / `put` / `add` / `addAll` / `remove` / `clear` / `[k] =` / `+=` / `-=`) inside a `@Composable` body that also reads it. This overlaps the 

- repeated broad recomposition smells across screens/components → [stability](https://developer.android.com/develop/ui/compose/performance/stability)

- raw `List`/`Map`/`Set` parameters on widely reused composables when the rest of the codebase has the immutable-collections dependency available — deduct when Strong Skipping is OFF (unstable params block skipping outright), or when Strong

- unstable composable params whose `equals()` is expensive, allocating, or semantically broken — for example, a plain `class Foo(...)` with identity equality passed to a reusable composable, a `data class` wrapping a large collection (deep 

- instance-recreation churn in source: `listOf(...)` / `mapOf(...)` / `setOf(...)` / anonymous `object` literals / `MyParams(...)` allocated inside a hot composable body and passed as a param. The value is `!=` to the prior recomposition's 

- `mutableStateOf<Int|Long|Float|Double>` where the typed factory exists (autoboxing) → [state](https://developer.android.com/develop/ui/compose/state)

- `derivedStateOf { ... }` whose block does not actually read any `State` object (meaning it will never invalidate, and the overhead of `derivedStateOf` is wasted) → [side-effects](https://developer.android.com/develop/ui/compose/side-effec

- `@NonSkippableComposable` / `@DontMemoize` opt-outs without a justifying comment → [strong skipping](https://developer.android.com/develop/ui/compose/performance/stability/strongskipping)

- if the project is on a Compose Compiler track older than 1.5.4 / Kotlin 2.0.20, stability matters more than the rules above assume — note this in the report and weight unstable-param findings more heavily → [strong skipping](https://devel

- `remember { … }` whose body reads `LocalConfiguration`, `LocalDensity`, or `LocalLayoutDirection` without declaring those values as keys — the cached value silently goes stale on rotation / foldable posture / font-scale changes → [state](

- `indexOf()` / `lastIndexOf()` / `indexOfFirst { }` called inside a `LazyListScope` item factory — O(n²) scroll cost and crash risk when identity moves; use `itemsIndexed` instead → [lists](https://developer.android.com/develop/ui/compose/

- `animateItemPlacement()` on Compose 1.7+ — replaced by `Modifier.animateItem()` → [lists](https://developer.android.com/develop/ui/compose/lists)

- Accompanist libraries where first-party replacements exist: `accompanist-pager` (→ `HorizontalPager`), `accompanist-swiperefresh` (→ `PullToRefreshBox`), `accompanist-flowlayout` (→ `FlowRow` / `FlowColumn`), `accompanist-systemuicontroll

- `Canvas` / `Spacer` with only `Modifier.fillMaxSize()` and no explicit height or aspect ratio — may enter draw with `Size.Zero`, producing `NaN` math and Skia-pipeline crashes. Require `Modifier.size(...)`, `Modifier.height(...)`, or `Mod

- lazy-list `key = { ... }` computed from a source that cannot guarantee uniqueness (merged flows, paginated streams, `hashCode()` on non-`data class`) — `IllegalArgumentException: Key ... was already used` crashes production. Verify with t

- `Animatable(...)` created inside a composable body without `remember { Animatable(...) }` (and not hoisted from a state holder) — the animation state is rebuilt on recomposition, which restarts the animation and drops in-flight velocity/t

- per-frame animated values read in the composition body and piped into non-lambda modifiers (`Modifier.offset(x.value.dp)`, `Modifier.alpha(alpha.value)`, `Modifier.rotate(rot.value)`). Every frame triggers recomposition of the caller inst

- `rememberInfiniteTransition()` hosted in a composable that stays in composition while offscreen (e.g. inside a `Scaffold` content that does not unmount on tab switch) — the animation keeps running until the host is removed from compositio

- several `animate*AsState` calls in the same composable all keyed off the same boolean/enum when `updateTransition` would keep them synchronized — light deduction when the drift is user-visible (alpha/scale/color finishing at different tim

- `LazyPagingItems` rendered with `items(count = …)` but **missing `key =`** or using **index-only keys** on a paginated/merged feed — reorder, refresh, and prepend can crash or thrash compositions → [paging compose](https://developer.andro

- treating `LazyPagingItems` like a materialized list (`itemSnapshotList` primary UI path, `forEach` into a nested lazy list) instead of the supported `items(count = …)` integration → [paging compose](https://developer.android.com/topic/lib

- clear single source of truth → [architecture](https://developer.android.com/develop/ui/compose/architecture)

- correct hoisting to the lowest common reader / highest writer → [state hoisting](https://developer.android.com/develop/ui/compose/state-hoisting)

- related state hoisted together when driven by the same events → [state hoisting](https://developer.android.com/develop/ui/compose/state-hoisting)

- stateless reusable composables with stateful wrappers where useful → [state hoisting](https://developer.android.com/develop/ui/compose/state-hoisting)

- `rememberSaveable` for UI state that should survive recreation → [state](https://developer.android.com/develop/ui/compose/state)

- custom `Saver` / `mapSaver` / `listSaver` / `@Parcelize` for non-bundleable types in `rememberSaveable` → [state](https://developer.android.com/develop/ui/compose/state)

- `collectAsStateWithLifecycle()` in Android UI code → [state](https://developer.android.com/develop/ui/compose/state)

- observable immutable state instead of mutable non-observable containers → [state](https://developer.android.com/develop/ui/compose/state)

- correct observable collections via `mutableStateListOf` / `mutableStateMapOf` instead of wrapping `mutableListOf`/`mutableMapOf` in a `MutableState` → [state](https://developer.android.com/develop/ui/compose/state)

- typed state factories (`mutableIntStateOf` and friends) — cross-listed with Performance because the failure mode is autoboxing → [state](https://developer.android.com/develop/ui/compose/state)

- plain state-holder classes when screen logic grows; idiomatic shape is `@Stable class FooState(...)` paired with a `@Composable fun rememberFooState(...): FooState` factory → [architecture](https://developer.android.com/develop/ui/compose

- ViewModel used as the source of truth for screen-level state, scoped at the screen level (not deep in the tree, not inside reusable components) → [architecture](https://developer.android.com/develop/ui/compose/architecture), [state](https

- ViewModel-exposed flows converted with `.stateIn(scope, SharingStarted.WhileSubscribed(5_000), initial)` — survives configuration changes without restarting upstream work → [architecture](https://developer.android.com/develop/ui/compose/a

- `remember(key)` invalidation when cached values depend on inputs → [state](https://developer.android.com/develop/ui/compose/state)

- duplicated or split ownership of state → [state hoisting](https://developer.android.com/develop/ui/compose/state-hoisting)

- under-hoisted shared state → [state hoisting](https://developer.android.com/develop/ui/compose/state-hoisting)

- reusable components with unnecessary internal state → [state hoisting](https://developer.android.com/develop/ui/compose/state-hoisting)

- misuse of `remember` where `rememberSaveable` is more appropriate → [state](https://developer.android.com/develop/ui/compose/state)

- non-observable mutable collections or mutable data holders used as state (`mutableListOf` held in a `var`, `ArrayList` mutated in place) → [state](https://developer.android.com/develop/ui/compose/state)

- `mutableListOf` / `mutableMapOf` wrapped in a `MutableState` where `mutableStateListOf` / `mutableStateMapOf` would correctly observe element changes → [state](https://developer.android.com/develop/ui/compose/state)

- Android flows collected in UI without lifecycle awareness when the code is Android-specific (skip on Compose Multiplatform code paths) → [state](https://developer.android.com/develop/ui/compose/state)

- state scattered across multiple sibling composables without a clear owner → [state hoisting](https://developer.android.com/develop/ui/compose/state-hoisting)

- `remember { computeFromInput(x) }` with no `key` — stale cached value when `x` changes → [state](https://developer.android.com/develop/ui/compose/state)

- `viewModel()` invoked deep in a composable tree (rather than at the screen entry point) or ViewModels passed via `CompositionLocal` → [architecture](https://developer.android.com/develop/ui/compose/architecture), [compositionlocal](https:

- `rememberSaveable { mutableStateOf(SomeNonBundleable(...)) }` without a `Saver` — restoration silently fails after process death → [state](https://developer.android.com/develop/ui/compose/state)

- string-based navigation routes (`composable("home")`, `navigate("profile/$id")`) on Navigation Compose 2.8+ where type-safe `@Serializable` routes are available — loses compile-time checking and encourages argument-encoding bugs → [naviga

- `mutableStateOf` held in a `ViewModel` instead of `StateFlow` / `MutableStateFlow` — couples the ViewModel to the Compose runtime and hurts testability. App-level teams may accept this tradeoff deliberately; note the tradeoff rather than 

- ViewModel-to-UI events modeled only as `Channel` / `SharedFlow` when the outcome must survive lifecycle gaps (snackbars, validation messages, navigation decisions). Prefer durable UI state with an acknowledgement callback for must-deliver

- `rememberSaveable` used inside a `LazyListScope` item factory (per-item expansion state, per-item form fields) — each entry is serialized into the saved-state `Bundle` which is capped at ~1 MB; large lists trigger `TransactionTooLargeExce

- paging UI that ignores `LazyPagingItems.loadState` — blank screen during initial refresh, stuck spinner, or silent failure with no `retry()` path → [paging compose](https://developer.android.com/topic/libraries/architecture/paging/v3-comp

- duplicate manual loading flags (`mutableStateOf(isLoading)`) shadowing `loadState` on paging screens — two sources of truth for the same UX → [paging compose](https://developer.android.com/topic/libraries/architecture/paging/v3-compose)

- `loadState.append is LoadState.Error` handled only as a spinner or not at all — append failures leave the user with no way to resume the feed; an append-error footer must offer `retry()` → [paging compose](https://developer.android.com/to

- `lazyPagingItems[index]!!` (or assuming every slot is non-null) — with `PagingConfig.enablePlaceholders = true`, slots are `null` while a page loads and `!!` NPE-crashes; the dual smell is a placeholder branch that can never run because p

- `loadState.refresh is LoadState.Error -> FullScreenError()` with **no `itemCount == 0` guard** — a transient pull-to-refresh failure then wipes an already-loaded feed and replaces it with a full-screen error. Full-screen error should gate

When Nav3 is detected (see playbook section 2b), also deduct for: - `entryDecorators` list supplied without re-adding `rememberSaveableStateHolderNavEntryDecorator()` — `rememberSaveable` inside entries silently stops persisting state → [Na

- `entryDecorators` list supplied without re-adding `rememberSaveableStateHolderNavEntryDecorator()` — `rememberSaveable` inside entries silently stops persisting state → [Nav3 save state](https://developer.android.com/guide/navigation/navi

- Anonymous or non-top-level `NavKey` destination types — breaks process-death restore and `rememberSaveable` for that entry → [Nav3](https://developer.android.com/guide/navigation/navigation-3)

- Feature/screen ViewModel owns or mutates the back stack directly — navigation lifecycle coupled to ViewModel, defeats predictive back and scene strategies → [Nav3](https://developer.android.com/guide/navigation/navigation-3)

- `ResultEventBus` / `conflateAsState` result treated as surviving process death — result is only available within the current navigation lifetime; persist in `SavedStateHandle` if survival is required → [Nav3 save state](https://developer.

All citations in this category point to the canonical [Side-effects in Compose](https://developer.android.com/develop/ui/compose/side-effects) page unless noted. The official docs put `derivedStateOf` and `snapshotFlow` under side-effects. 

- side-effect-free composition → [side-effects](https://developer.android.com/develop/ui/compose/side-effects)

- correct use of `LaunchedEffect`, `DisposableEffect`, `SideEffect`, `rememberUpdatedState`, and `produceState` → [side-effects](https://developer.android.com/develop/ui/compose/side-effects)

- effects keyed to the right lifecycle inputs → [side-effects](https://developer.android.com/develop/ui/compose/side-effects)

- cleanup for listeners, observers, and subscriptions → [side-effects](https://developer.android.com/develop/ui/compose/side-effects)

- stale callback capture avoided with `rememberUpdatedState` when needed → [side-effects](https://developer.android.com/develop/ui/compose/side-effects)

- `snapshotFlow { … }` collected from inside a `LaunchedEffect` for Compose-state → Flow conversions → [side-effects](https://developer.android.com/develop/ui/compose/side-effects)

- `rememberCoroutineScope()` used only for event-driven work (button taps, gesture handlers); long-lived/keyed work lives in `LaunchedEffect` → [side-effects](https://developer.android.com/develop/ui/compose/side-effects)

- navigation, snackbar, analytics, and repository calls live in event handlers or `LaunchedEffect`, never in the composition body → [side-effects](https://developer.android.com/develop/ui/compose/side-effects), [navigation](https://develope

- image loading delegated to threading-aware loaders (Coil, Glide) via their Compose integration APIs (`AsyncImage`, `rememberAsyncImagePainter`) — these manage the threading contract correctly and are the accepted carve-out from "no IO in 

- suspending UI / ViewModel paths preserve structured cancellation: broad catches and `runCatching` rethrow `CancellationException` before converting failures into UI state → [coroutines](https://developer.android.com/kotlin/coroutines/coro

- `Animatable.animateTo(...)` / `snapTo(...)` driven from a `LaunchedEffect(key)` so the animation cancels on key change and on composition exit → [animation](https://developer.android.com/develop/ui/compose/animation/value-based), [side-ef

- declarative targets use `animate*AsState` and leave coroutine management to Compose; manual `rememberCoroutineScope().launch { ... }` is reserved for event-driven or gesture-driven animation → [animation](https://developer.android.com/dev

- launching threads, coroutines, navigation, or external work directly in composition → [side-effects](https://developer.android.com/develop/ui/compose/side-effects) - **strictly forbidden IO in a composable body** — never appears in compos

- **strictly forbidden IO in a composable body** — never appears in composition regardless of how it is wrapped (`remember` does not redeem it, since the work still runs on the composition thread on first composition and on every key change

- wrong effect API choice → [side-effects](https://developer.android.com/develop/ui/compose/side-effects)

- incorrect or missing effect keys → [side-effects](https://developer.android.com/develop/ui/compose/side-effects)

- stale captures in long-lived effects → [side-effects](https://developer.android.com/develop/ui/compose/side-effects)

- empty or suspicious `onDispose` → [side-effects](https://developer.android.com/develop/ui/compose/side-effects)

- listeners or observers registered without cleanup → [side-effects](https://developer.android.com/develop/ui/compose/side-effects)

- `snapshotFlow { … }` invoked outside an effect, or used to compute values that `derivedStateOf` would handle more cheaply → [side-effects](https://developer.android.com/develop/ui/compose/side-effects)

- `rememberCoroutineScope()` used to launch work that should live in a keyed `LaunchedEffect` (manual cancellation, lifecycle handling reinvented) → [side-effects](https://developer.android.com/develop/ui/compose/side-effects)

- `derivedStateOf { a + b }`-style misuse where inputs change as often as outputs — pure overhead per the official guidance → [side-effects](https://developer.android.com/develop/ui/compose/side-effects)

- `LaunchedEffect(Unit)` / `LaunchedEffect(true)` flagged only when the body captures parameter or state values that may change without being keyed or wrapped in `rememberUpdatedState`. The "run once on enter" pattern itself is idiomatic; d

- `rememberUpdatedState` read eagerly inside `remember { ... }` and assigned to a captured local before invocation — the remembered object keeps the initial callback/value forever. Read the `State.value` at invocation time or key the rememb

- `runCatching { ... }`, `catch (Exception)`, or `catch (Throwable)` around suspend calls without rethrowing `CancellationException` — cancellation is converted into an error state instead of propagating through the coroutine hierarchy → [c

- `navController.navigate(...)` invoked from the composition body instead of an event handler or effect → [navigation](https://developer.android.com/develop/ui/compose/navigation)

- `rememberCoroutineScope().launch { animatable.animateTo(target) }` where a `LaunchedEffect(target) { animatable.animateTo(target) }` would more clearly express target-driven animation — prefer `LaunchedEffect(target)` when restart semanti

- `Animatable.animateTo(...)` invoked from the composition body (not from inside an effect) — runs on every recomposition and never cancels → [animation](https://developer.android.com/develop/ui/compose/animation/value-based), [side-effects

- unconditional `lazyPagingItems.refresh()` / `retry()` from the composable body or bare `LaunchedEffect(Unit)` without a documented one-shot reason — initial load belongs to `PagingData`; refresh is user-driven → [paging compose](https://d

When Nav3 is detected (see playbook section 2b), also deduct for: - `backStack.add` / `backStack.removeLastOrNull` called directly in the composition body instead of inside an event handler or `LaunchedEffect` — navigation fires on every re

- `backStack.add` / `backStack.removeLastOrNull` called directly in the composition body instead of inside an event handler or `LaunchedEffect` — navigation fires on every recomposition → [Nav3](https://developer.android.com/guide/navigatio

- Tap handler missing `dropUnlessResumed { backStack.add(...) }` — a queued tap can navigate from a screen already in exit animation, duplicating the back-stack entry → [Nav3](https://developer.android.com/guide/navigation/navigation-3)

This category is lighter-touch for app repositories. Focus on shared internal components, UI kits, and reusable building blocks. The two authoritative sources are the [Compose API guidelines](https://developer.android.com/develop/ui/compose

- reusable components expose `modifier: Modifier = Modifier` → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-component-api-guidelines.md)

- `modifier` is the first optional parameter and applied once as the first link in the chain on the root-most UI node → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-compon

- parameter order is sensible: required, `modifier`, optional, trailing content lambda → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-component-api-guidelines.md)

- defaults are meaningful and not hidden behind nullable sentinel behavior; defaults exposed through a `ComponentDefaults` object → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/co

- explicit parameters preferred over component-specific `CompositionLocal` indirection. `CompositionLocal` is appropriate for *tree-scoped* data with sensible defaults (theme tokens like `LocalContentColor`, `LocalTextStyle`); not appropria

- components are focused and layered instead of multipurpose grab-bags → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-component-api-guidelines.md)

- slot APIs (`content: @Composable RowScope.() -> Unit`) used for flexible composition; receiver scopes (`RowScope`, `ColumnScope`, `BoxScope`) applied where they guide layout → [component API](https://android.googlesource.com/platform/fram

- `Basic*` naming for unstyled / minimal variants alongside the opinionated public version (e.g. `BasicTextField` ↔ `TextField`) → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/com

- distinct components for visual variants (`ContainedButton`, `OutlinedButton`, `TextButton`) instead of a single component with a `style` enum → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-main/c

- `@Composable` functions are PascalCase and Unit-returning where they emit UI → [api-guidelines](https://developer.android.com/develop/ui/compose/api-guidelines)

- UI-emitting composables either emit UI or report via callbacks/state holders, but do not also return handles or computed values → [api-guidelines](https://developer.android.com/develop/ui/compose/api-guidelines)

- reusable content composables emit a cohesive root node, or explicitly declare a parent-layout scope when they intentionally emit multiple siblings → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-m

- event callbacks are named and positioned as events (`onClick`, `onValueChange`) while trailing lambdas are reserved for composable content slots → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-mai

- custom modifiers built with `Modifier.Node` rather than the discouraged `composed { }` factory → [custom modifiers](https://developer.android.com/develop/ui/compose/custom-modifiers)

- `movableContentOf` / `movableContentWithReceiverOf` used to preserve slot-content lifecycle when content moves between containers → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/

- reusable APIs prefer `value: T` (immediate read) or `value: () -> T` (deferred read) plus `onValueChange: (T) -> Unit` over `MutableState<T>` parameters → [component API](https://android.googlesource.com/platform/frameworks/support/+/andr

- isolated components define `@Preview` configurations to prove they render stateless → [tooling](https://developer.android.com/develop/ui/compose/tooling/previews)

- reusable animated components expose `animationSpec: AnimationSpec<T> = spring()` (or another appropriate default) when callers may reasonably need timing control, and use meaningful labels on shared/tooling-visible animations → [animation

- shared components missing `modifier` → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-component-api-guidelines.md)

- multiple modifier params or modifier applied to the wrong child (anywhere other than the root-most emitted layout) → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-compone

- hardcoded strings in UI elements (e.g. `Text("Share with friends")` instead of `stringResource(id = R.string...)`) which break i18n support and create brittle tests → [resources](https://developer.android.com/develop/ui/compose/resources)

- hardcoded magic numbers like `.padding(12.dp)` or `.size(24.sp)` or explicit `Color(0xFF...)` instead of routing through `MaterialTheme` tokens or `dimensionResource`. A clean theme is vital for dark mode and accessibility → [theming](htt

- no `@Preview` coverage for extracted UI chunks. If a component is reusable, it should have a preview proving it has no hidden ambient dependencies → [tooling](https://developer.android.com/develop/ui/compose/tooling/previews)

- `modifier` with a non-no-op default like `Modifier.padding(8.dp)` (caller's modifier silently loses the padding) → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-component

- parameter ordering that makes APIs awkward or misleading → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-component-api-guidelines.md)

- nullable params used only as "use internal default" signals — expose the default explicitly via a `ComponentDefaults` object instead → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/do

- passing raw network models, database entities, or complex domain objects directly into UI components instead of mapping them to stable, UI-specific presentation models (UiState). This leaks backend structure into the presentation tier, en

- `MutableState<T>` or `State<T>` params in reusable APIs when avoidable; the official replacement is `value: T` or `value: () -> T` plus `onValueChange: (T) -> Unit` → [component API](https://android.googlesource.com/platform/frameworks/su

- giant multipurpose components that should be split or wrapped → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-component-api-guidelines.md)

- UI-emitting composables that return non-`Unit` values or handles. Report state via callbacks / state holders; keep value-returning composables value-only → [api-guidelines](https://developer.android.com/develop/ui/compose/api-guidelines)

- reusable content composables that emit multiple sibling roots without an explicit parent scope such as `RowScope` or `ColumnScope`; wrap in a cohesive root layout or make the scope contract explicit → [component API](https://android.googl

- pure helpers marked `@Composable` even though they neither read composition data nor emit UI, or `@ReadOnlyComposable` applied to functions that emit UI / launch effects / mutate state → [api-guidelines](https://developer.android.com/deve

- event callbacks placed as the trailing lambda so call sites read like content slots, or callbacks named as past-tense notifications when Compose-style `onXxx` event names would make the contract clearer → [component API](https://android.g

- behavior added as parameters that should be modifiers (`onClick`, `clipToCircle`) → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-component-api-guidelines.md)

- style/configuration objects passed to a single component instead of distinct components per variant → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-component-api-guidelin

- non-Compose lifecycles attached to composables — for example, an `onClick` callback on a layout component when `Modifier.clickable` would do → [component API](https://android.googlesource.com/platform/frameworks/support/+/androidx-main/co

- modifier ordering that quietly changes semantics in shared components (e.g. `Modifier.padding(...).clickable {}` extends the click region into the padding; `Modifier.clickable {}.padding(...)` does not). Flag when the choice looks acciden

- hardcoded `dp`, `sp`, or explicit `Color` constructs in reusable components instead of using `MaterialTheme.colorScheme`, `MaterialTheme.typography`, or dimension resources; this destroys dark mode compliance and accessible font scaling →

- `CompositionLocal` used for component-specific configuration (vs. truly tree-scoped data); ViewModels stored in `CompositionLocal`; locals with no sensible default → [compositionlocal](https://developer.android.com/develop/ui/compose/comp

- custom modifiers built with `Modifier.composed { }` when `Modifier.Node` would do — `composed { }` is officially discouraged for performance → [custom modifiers](https://developer.android.com/develop/ui/compose/custom-modifiers)

- `Scaffold { innerPadding -> ... }` content that does not apply `innerPadding` to its root child (or consume it via `consumeWindowInsets`) — content draws behind the `TopAppBar` / `BottomAppBar` / system bars → [component API](https://andr

- highly reusable animated composables that hard-code `tween(N)` / specific `spring()` stiffness in the signature when callers would reasonably need control over timing — consider exposing `animationSpec: AnimationSpec<T>` instead → [animat

- shared/tooling-visible `animate*AsState` / `updateTransition` call sites missing a meaningful `label` parameter — reduces clarity in Animation Preview and other Android Studio tooling; treat as a light deduction, not a hard failure → [ani

- Evidence: theme file line, referenced resource, resolved drawable file, and missing/present `drawable-v31` override. - Fix direction: keep the same `@drawable/name` in the theme and make it resolve to an `<animated-vector>` on API 31+ tha

- References: `https://developer.android.com/develop/ui/views/launch/splash-screen`, `https://developer.android.com/reference/androidx/core/splashscreen/SplashScreen`, and the platform issue `https://issuetracker.google.com/issues/520672537

Severity: **Should-fix**, promoted to a **Critical Finding** when the loop is per-frame (resize/scroll/animation-driven) or spans reused lazy items. For shape 1, cite the writer's `file:line` and the reader's `file:line`. Docs: [phases](htt