Compose Ui

new-silvermoon/awesome-android-agent-skills

This surfaces all the canonical Jetpack Compose patterns in one place: state hoisting with value/onValueChange pairs, modifier parameters as first optional arg, remember versus derivedStateOf for performance, and theming through MaterialTheme instead of hardcoded values. You'd invoke this when writing new Composables or refactoring existing ones that feel janky or hard to test. The guidance is opinionated but correct, especially the lambda stability notes and the insistence on stateless components wherever possible. If you're past the tutorial phase but still occasionally wonder why your list stutters or your previews break, this will catch most of the gotchas before they ship.

skills.sh installs: 760
GitHub stars: 1K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add new-silvermoon/awesome-android-agent-skills --skill compose-ui --agent claude-code

Installs into .claude/skills of the current project.

Files

Jetpack Compose Best Practices

Instructions

Follow these guidelines to create performant, reusable, and testable Composables.

1. State Hoisting (Unidirectional Data Flow)

Make Composables stateless whenever possible by moving state to the caller.

Pattern: Function signature should usually look like:

@Composable
fun MyComponent(
    value: String,              // State flows down
    onValueChange: (String) -> Unit, // Events flow up
    modifier: Modifier = Modifier // Standard modifier parameter
)

Benefit: Decouples the UI from simple state storage, making it easier to preview and test.
ViewModel Integration: The screen-level Composable retrieves state from the ViewModel (viewModel.uiState.collectAsStateWithLifecycle()) and passes it down.

SKILL.md on GitHub