migrate-xml-views-to-jetpack-compose

Follow a structured process: analyze the layout and project, set up Compose dependencies and theming, convert the XML hierarchy to composables with matching modifiers, add a Compose Preview, validate against a baseline screenshot, replace usages, then delete the XML. This skill automates that ten-step workflow.

Use ComposeView inside your XML layout or Fragment and call setContent with your composable, setting an appropriate ViewCompositionStrategy. For full screens, call setContent directly in a ComponentActivity with the activity-compose dependency.

Yes, use the AndroidView composable to embed Views not yet available in Compose, or AndroidViewBinding to inflate XML layouts with view binding. For lazy lists, use the AndroidView overload with onReset to enable View reuse.

Map XML color attributes to Material 3 semantic roles like primary and surface, then define ColorScheme, Typography, and Shapes objects for MaterialTheme. Reuse existing XML values as the source of truth and never hardcode new values.

Start with leaf-node layouts that have minimal nesting, few state variables, low reuse across the project, and no complex external dependencies. These self-contained components carry the lowest regression risk during incremental adoption.