Android Jetpack Compose

Standards for Declarative UI, State Hoisting, and Performance Use when this capability is needed.

tomevault-io fc44a3a 2 files · 1.9 KB Updated

File contents

Jetpack Compose Standards

Priority: P0

Implementation Guidelines

State Hoisting

  • Pattern: Screen (Stateful) -> Content (Stateless).
  • Events: Pass lambda callbacks down (onItemClick: (Id) -> Unit).
  • Dependencies: NEVER pass ViewModel to stateless composables.

Performance

  • Recomposition: Use @Stable / @Immutable on UI Models.
  • Lists: Always use key in LazyColumn / LazyRow.
  • Modifiers: Reuse Modifier instances or extract to variables if stable.

Theming (Material 3)

  • Tokens: Use MaterialTheme.colorScheme and MaterialTheme.typography.
  • Hardcoding: **No Hardcoded Colors**: Use Theme.

Anti-Patterns

  • Side Effects: **No SideEffects in Composition**: Use LaunchedEffect.
  • ViewModel pass-through: **No VM deep pass**: Hoist state.

References

  • Patterns & Optimization

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

tomevault-io/skills-registry/tree/main/fierzone--agent-skills-standard--compose commit fc44a3a6bf

Frequently asked questions

npx skillmds@latest add tomevault-io/android-jetpack-compose