Agent skill · software engineering · aiskillstore
android-jetpack-compose-expert
Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3.
Why this skill is useful
Provides specific architectural patterns and state management techniques for Jetpack Compose that the AI wouldn't reliably generate on its own.
What it needs
Requires android-sdk installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Android Jetpack Compose Expert Overview A comprehensive guide for building production-quality Android applications using Jetpack Compose. This skill covers architectural patterns, state management with ViewModels, navigation type-safety, and performance optimization techniques. When to Use This Skill Use when starting a new Android project with Jetpack Compose. Use when migrating legacy XML layouts to Compose. Use when implementing complex UI state management and side effects. Use when optimizing Compose performance (recomposition counts, stability). Use when setting up Navigation with type safety. Step-by-Step Guide 1. Project Setup & Dependencies Ensure your libs.versions.toml includes the necessary Compose BOM and libraries. 2. State Management Pattern (MVI/MVVM) Use ViewModel with StateFlow to expose UI state. Avoid exposing MutableStateFlow. 3. Creating the Screen Composable Consume the state in a "Screen" composable and pass data down to stateless components. Examples Example 1: Type-Safe Navigation Using the new Navigation Compose Type Safety (available in recent versions). Best Practices ✅ Do: Use remember and derivedStateOf to minimize unnecessary calculations during recomposition. ✅ Do: Mark data classes used in UI state as @Immutable or @Stable if they contain List or other unstable types to enable smart recomposition skipping. ✅ Do: Use LaunchedEffect for one-off side effects (like showing a Snackbar) triggered by state changes. ❌ Don't: Perform expensive operations (like sorting a list) directly inside the Composable function body without remember. ❌ Don't: Pass ViewModel instances down to child components. Pass only the data (state) and lambda callbacks (events). Troubleshooting Problem: Infinite Recomposition loop. Solution: Check if you are creating new object instances (like List or Modifier) inside the composition without remember, or if you are updating state inside the composition phase instead of a side-effect or callback. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/android-jetpack-compose-expert