
xml-to-compose-migration
Convert Android XML layouts to Jetpack Compose. Use when asked to migrate Views to Compose, convert XML to Composables, or modernize UI from View system to Compose.
- Installs
- 433
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/new-silvermoon/awesome-android-agent-skills --skill xml-to-compose-migration- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads xml-to-compose-migration automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
XML to Compose Migration
Overview
Systematically convert Android XML layouts to idiomatic Jetpack Compose, preserving functionality while embracing Compose patterns. This skill covers layout mapping, state migration, and incremental adoption strategies.
Workflow
1. Analyze the XML Layout
- Identify the root layout type (
ConstraintLayout,LinearLayout,FrameLayout, etc.). - List all View widgets and their key attributes.
- Map data binding expressions (
@{}) or view binding references. - Identify custom views that need special handling.
- Note any
include,merge, orViewStubusage.
2. Plan the Migration
- Decide: Full rewrite or incremental migration (using
ComposeView/AndroidView). - Identify state sources (ViewModel, LiveData, savedInstanceState).
- List reusable components to extract as separate Composables.
- Plan navigation integration if using Navigation component.
3. Convert Layouts
Apply the layout mapping table below to convert each View to its Compose equivalent.
4. Migrate State
- Convert
LiveDataobservation toStateFlowcollection orobserveAsState(). - Replace
findViewById/ ViewBinding with Compose state. - Convert click listeners to lambda parameters.
5. Test and Verify
- Compare visual output between XML and Compose versions.
- Test accessibility (content descriptions, touch targets).
- Verify state preservation across configuration changes.
Layout Mapping Reference
Container Layouts
| XML Layout | Compose Equivalent | Notes |
|---|---|---|
LinearLayout (vertical) | Column | Use Arrangement and Alignment |
LinearLayout (horizontal) | Row | Use Arrangement and Alignment |
FrameLayout | Box | Children stack on top of each other |
ConstraintLayout | ConstraintLayout (Compose) | Use createRefs() and constrainAs |
RelativeLayout | Box or ConstraintLayout | Prefer Box for simple overlap |
ScrollView | Column + Modifier.verticalScroll() | Or use LazyColumn for lists |
HorizontalScrollView | Row + Modifier.horizontalScroll() | Or use LazyRow for lists |
RecyclerView | LazyColumn / LazyRow / LazyGrid | Most common migration |
ViewPager2 | HorizontalPager | From accompanist or Compose Foundation |
CoordinatorLayout | Custom + Scaffold | Use TopAppBar with scroll behavior |
NestedScrollView | Column + Modifier.verticalScroll() | Prefer Lazy variants |
Common Widgets
| XML Widget | Compose Equivalent | Notes |
|---|---|---|
TextView | Text | Use style → TextStyle |
EditText | TextField / OutlinedTextField | Requires state hoisting |
Button | Button | Use onClick lambda |
ImageView | Image | Use painterResource() or Coil |
ImageButton | IconButton | Use Icon inside |
CheckBox | Checkbox | Requires checked + onCheckedChange |
RadioButton | RadioButton | Use with Row for groups |
Switch | Switch | Requires state hoisting |
ProgressBar (circular) | CircularProgressIndicator | |
ProgressBar (horizontal) | LinearProgressIndicator | |
SeekBar | Slider | Requires state hoisting |
Spinner | DropdownMenu + ExposedDropdownMenuBox | More complex pattern |
CardView | Card | From Material 3 |
Toolbar | TopAppBar | Use inside Scaffold |
BottomNavigationView | NavigationBar | Material 3 |
FloatingActionButton | FloatingActionButton | Use inside Scaffold |
Divider | HorizontalDivider / VerticalDivider | |
Space | Spacer | Use Modifier.size() |
Attribute Mapping
| XML Attribute | Compose Modifier/Property |
|---|---|
android:layout_width="match_parent" | Modifier.fillMaxWidth() |
android:layout_height="match_parent" | Modifier.fillMaxHeight() |
android:layout_width="wrap_content" | Modifier.wrapContentWidth() (usually implicit) |
android:layout_weight | Modifier.weight(1f) |
android:padding | Modifier.padding() |
android:layout_margin | Modifier.padding() on parent, or use Arrangement.spacedBy() |
android:background | Modifier.background() |
android:visibility="gone" | Conditional composition (don't emit) |
android:visibility="invisible" | Modifier.alpha(0f) (keeps space) |
android:clickable | Modifier.clickable { } |
android:contentDescription | Modifier.semantics { contentDescription = "" } |
android:elevation | Modifier.shadow() or component's elevation param |
android:alpha | Modifier.alpha() |
android:rotation | Modifier.rotate() |
android:scaleX/Y | Modifier.scale() |
android:gravity | Alignment parameter or Arrangement |
android:layout_gravity | Modifier.align() |
Common Patterns
LinearLayout with Weights
<!-- XML -->
<LinearLayout android:orientation="horizontal">
<View android:layout_weight="1" />
<View android:layout_weight="2" />
</LinearLayout>
// Compose
Row(modifier = Modifier.fillMaxWidth()) {
Box(modifier = Modifier.weight(1f))
Box(modifier = Modifier.weight(2f))
}
RecyclerView to LazyColumn
<!-- XML -->
<androidx.recyclerview.widget.RecyclerView
android:id="@+id/recyclerView"
android:layout_width="match_parent"
android:layout_height="match_parent" />
// Compose
LazyColumn(modifier = Modifier.fillMaxSize()) {
items(items, key = { it.id }) { item ->
ItemRow(item = item, onClick = { onItemClick(item) })
}
}
EditText with Two-Way Binding
<!-- XML with Data Binding -->
<EditText
android:text="@={viewModel.username}"
android:hint="@string/username_hint" />
// Compose
val username by viewModel.username.collectAsState()
OutlinedTextField(
value = username,
onValueChange = { viewModel.updateUsername(it) },
label = { Text(stringResource(R.string.username_hint)) },
modifier = Modifier.fillMaxWidth()
)
ConstraintLayout Migration
<!-- XML -->
<androidx.constraintlayout.widget.ConstraintLayout>
<TextView
android:id="@+id/title"
app:layout_constraintTop_toTopOf="parent"
app:layout_constraintStart_toStartOf="parent" />
<TextView
android:id="@+id/subtitle"
app:layout_constraintTop_toBottomOf="@id/title"
app:layout_constraintStart_toStartOf="@id/title" />
</androidx.constraintlayout.widget.ConstraintLayout>
// Compose
ConstraintLayout(modifier = Modifier.fillMaxWidth()) {
val (title, subtitle) = createRefs()
Text(
text = "Title",
modifier = Modifier.constrainAs(title) {
top.linkTo(parent.top)
start.linkTo(parent.start)
}
)
Text(
text = "Subtitle",
modifier = Modifier.constrainAs(subtitle) {
top.linkTo(title.bottom)
start.linkTo(title.start)
}
)
}
Include / Merge → Extract Composable
<!-- XML: layout_header.xml -->
<merge>
<ImageView android:id="@+id/avatar" />
<TextView android:id="@+id/name" />
</merge>
<!-- Usage -->
<include layout="@layout/layout_header" />
// Compose: Extract as a reusable Composable
@Composable
fun HeaderSection(
avatarUrl: String,
name: String,
modifier: Modifier = Modifier
) {
Row(modifier = modifier) {
AsyncImage(model = avatarUrl, contentDescription = null)
Text(text = name)
}
}
// Usage
HeaderSection(avatarUrl = user.avatar, name = user.name)
Incremental Migration (Interop)
Embedding Compose in XML
<!-- In your XML layout -->
<androidx.compose.ui.platform.ComposeView
android:id="@+id/compose_view"
android:layout_width="match_parent"
android:layout_height="wrap_content" />
// In Fragment/Activity
binding.composeView.setContent {
MaterialTheme {
MyComposable()
}
}
Embedding XML Views in Compose
// Use AndroidView for Views that don't have Compose equivalents
@Composable
fun MapViewComposable(modifier: Modifier = Modifier) {
AndroidView(
factory = { context ->
MapView(context).apply {
// Initialize the view
}
},
update = { mapView ->
// Update the view when state changes
},
modifier = modifier
)
}
State Migration
LiveData to Compose
// Before: Observing in Fragment
viewModel.uiState.observe(viewLifecycleOwner) { state ->
binding.title.text = state.title
}
// After: Collecting in Compose
@Composable
fun MyScreen(viewModel: MyViewModel = hiltViewModel()) {
val uiState by viewModel.uiState.collectAsStateWithLifecycle()
Text(text = uiState.title)
}
Click Listeners
// Before: XML + setOnClickListener
binding.submitButton.setOnClickListener {
viewModel.submit()
}
// After: Lambda in Compose
Button(onClick = { viewModel.submit() }) {
Text("Submit")
}
Checklist
- All layouts converted (no
includeormergeleft) - State hoisted properly (no internal mutable state for user input)
- Click handlers converted to lambdas
- RecyclerView adapters removed (using LazyColumn/LazyRow)
- ViewBinding/DataBinding removed
- Navigation integrated (NavHost or interop)
- Theming applied (MaterialTheme)
- Accessibility preserved (content descriptions, touch targets)
- Preview annotations added for development
- Old XML files deleted
References
FAQ
What does the xml-to-compose-migration skill do?
Convert Android XML layouts to Jetpack Compose. Use when asked to migrate Views to Compose, convert XML to Composables, or modernize UI from View system to Compose.
How do I install xml-to-compose-migration?
Run npx skills add https://github.com/new-silvermoon/awesome-android-agent-skills --skill xml-to-compose-migration in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/xml-to-compose-migration/ (personal) or .claude/skills/xml-to-compose-migration/ (project).
Which AI agents can use xml-to-compose-migration?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is xml-to-compose-migration safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains xml-to-compose-migration?
It is published by new-silvermoon in new-silvermoon/awesome-android-agent-skills. It has 433 recorded installs.
More from new-silvermoon/awesome-android-agent-skills
android-testing
new-silvermoon/awesome-android-agent-skills
Comprehensive testing strategy involving Unit, Integration, Hilt, and Screenshot tests.
gradle-build-performance
new-silvermoon/awesome-android-agent-skills
Debug and optimize Android/Gradle build performance. Use when builds are slow, investigating CI/CD performance, analyzing build scans, or identifying compilation bottlenecks.
compose-ui
new-silvermoon/awesome-android-agent-skills
Best practices for building UI with Jetpack Compose, focusing on state hoisting, detailed performance optimizations, and theming. Use this when writing or refactoring Composable functions.
android-gradle-logic
new-silvermoon/awesome-android-agent-skills
Expert guidance on setting up scalable Gradle build logic using Convention Plugins and Version Catalogs.
android-architecture
new-silvermoon/awesome-android-agent-skills
Expert guidance on setting up and maintaining a modern Android application architecture using Clean Architecture and Hilt. Use this when asked about project structure, module setup, or dependency injection.
kotlin-concurrency-expert
new-silvermoon/awesome-android-agent-skills
Kotlin Coroutines review and remediation for Android. Use when asked to review concurrency usage, fix coroutine-related bugs, improve thread safety, or resolve lifecycle issues in Kotlin/Android code.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.