jetpack-compose-skills

Why use it

Key features

@Composable structure and state-hoisting discipline
Material 3 theming defaults
ViewModel + StateFlow + collectAsStateWithLifecycle patterns
Compose navigation (navigation-compose) conventions
Preview and test authoring that actually runs

Live Demo

What it looks like in practice

jetpack-compose-skill.replay ▶ ready

0/0

Install

Author repository · Claude Skills documentation

Use Cases

Real-world ways to use jetpack-compose-skills

How to build a new Compose screen with state hoisting

👤 Android developers writing Compose UI ⏱ ~30 min intermediate

When to use: New screen in a Compose app — get it right the first time rather than refactoring later.

Flow

Describe the screen

Build a Profile screen: avatar, name, bio, follow button. State comes from a ProfileViewModel.✓ Copied

→ Stateless composable + stateful wrapper + preview
Wire the ViewModel

Hook up the ViewModel using collectAsStateWithLifecycle.✓ Copied

→ Lifecycle-aware state collection
Add a preview

Add @Preview variants for empty, loaded, and error states.✓ Copied

→ Three previews rendering without a live ViewModel

Outcome: A clean Compose screen with previews and a testable structure.

Pitfalls

Stateful composables you can't preview — Keep the composable stateless; hoist state to a wrapper
Wrong Modifier order — Skill prompts the order rule — padding before background for a padded background, etc.

Combine with: filesystem

Migrate a Views-based screen to Compose

👤 Teams converting legacy Android screens ⏱ ~90 min advanced

When to use: You want to convert one screen at a time without rewriting the whole app.

Flow

Map the XML

Here's fragment_profile.xml. Map each widget to a Compose equivalent with notes on behaviors to preserve.✓ Copied

→ XML → Compose mapping with behavior notes
Rewrite

Produce the Compose screen. Keep state + actions identical to the Fragment.✓ Copied

→ Composable file + ViewModel untouched
Keep the navigation hybrid if needed

Swap only this screen, leave the rest on Fragments using ComposeView.✓ Copied

→ Hybrid navigation continues to work

Outcome: One screen cleanly ported without destabilizing the rest.

Pitfalls

Observer leaks when mixing with Fragment lifecycle — Use viewLifecycleOwner with ComposeView; release on destroy

Combine with: android

Combinations

Pair with other MCPs for X10 leverage

jetpack-compose-skill + android

Run the resulting screen in an emulator and iterate

Build the app, launch in the emulator, and show me the Profile screen.✓ Copied

jetpack-compose-skill + filesystem

Work across modules in a Compose project

Read feature/profile/ and add a Profile screen in ui/.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call
compose-authoring	screen intent + state	Any new Compose UI
state-hoisting-review	existing composable	When a composable is hard to preview
view-to-compose-migration	XML + behaviors	Screen-by-screen migrations

Cost & Limits

What this costs to run

API quota: none
Tokens per call: 3–15k per screen
Monetary: free
Tip: Scope to one screen + its ViewModel at a time

Security

Permissions, secrets, blast radius

Credential storage: none at skill level

Data egress: none

Troubleshooting

Common errors and fixes

Preview fails to render

Make composables stateless; drop the ViewModel from the preview path.

StateFlow not collecting on background

Use collectAsStateWithLifecycle, not collectAsState, on screens that may be backgrounded.

Alternatives