Agent skill
xml-to-compose
Convert Android XML layouts to Jetpack Compose. Use when asked to migrate XML layouts, convert views to composables, or help with Compose migration. Handles layouts, widgets, attributes, styles, and resource references.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/xml-to-compose-skill
SKILL.md
XML to Jetpack Compose Converter
Convert Android XML layouts to idiomatic Jetpack Compose code.
Conversion Process
- Analyze the XML structure and identify root layout
- Map each view to its Compose equivalent
- Convert attributes to Modifier chains (order matters!)
- Handle resource references (@string, @dimen, @color)
- Extract styles into reusable composables or theme values
Quick Reference
Layouts
| XML | Compose |
|---|---|
LinearLayout (vertical) |
Column |
LinearLayout (horizontal) |
Row |
FrameLayout |
Box |
ConstraintLayout |
Column/Row or ConstraintLayout (dependency) |
ScrollView |
Column + Modifier.verticalScroll() |
RecyclerView |
LazyColumn / LazyRow |
ViewPager2 |
HorizontalPager |
Common Widgets
| XML | Compose |
|---|---|
TextView |
Text |
EditText |
TextField / OutlinedTextField |
Button |
Button |
ImageView |
Image / AsyncImage (Coil) |
CheckBox |
Checkbox |
Switch |
Switch |
ProgressBar |
CircularProgressIndicator / LinearProgressIndicator |
CardView |
Card |
Modifier Order
Order matters! Follow this sequence:
clickable/toggleablepadding(outer)size/fillMaxWidth/weightbackground/clipborderpadding(inner)
Detailed Mappings
See reference files for complete mappings:
references/layouts.md— Layout containersreferences/widgets.md— UI componentsreferences/attributes.md— XML attributes to Modifiers
Output Guidelines
- Use Material 3 — Import from
androidx.compose.material3 - Prefer built-in modifiers — Avoid custom implementations
- Handle nullability — XML allows null text, Compose needs defaults
- Extract dimensions — Use
dimensionResource()or define in theme - Keep composables stateless — Hoist state to caller
- Add Preview — Include
@Previewfunction for each composable
Example
Input:
<LinearLayout
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:orientation="vertical"
android:padding="16dp">
<TextView
android:id="@+id/title"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="@string/welcome"
android:textSize="24sp"
android:textStyle="bold"/>
<Button
android:id="@+id/action_button"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_marginTop="8dp"
android:text="@string/get_started"/>
</LinearLayout>
Output:
@Composable
fun WelcomeSection(
onGetStartedClick: () -> Unit,
modifier: Modifier = Modifier
) {
Column(
modifier = modifier
.fillMaxWidth()
.padding(16.dp)
) {
Text(
text = stringResource(R.string.welcome),
fontSize = 24.sp,
fontWeight = FontWeight.Bold
)
Spacer(modifier = Modifier.height(8.dp))
Button(
onClick = onGetStartedClick,
modifier = Modifier.fillMaxWidth()
) {
Text(text = stringResource(R.string.get_started))
}
}
}
@Preview(showBackground = true)
@Composable
private fun WelcomeSectionPreview() {
WelcomeSection(onGetStartedClick = {})
}
Key conversions:
match_parent→fillMaxWidth()/fillMaxHeight()wrap_content→ default (no modifier needed)layout_marginTop→Spacerbetween elements- Click listeners → lambda parameters
- IDs → not needed (state hoisting instead)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?