xml-to-compose-migration

Convert Android XML layouts into Jetpack Compose equivalents.

Updated Nov 3, 2025
One-click install
npx skills add https://github.com/devanfer02/telnetquiz --skill xml-to-compose-migration-devanfer02
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xml-to-compose-migration
Source: https://github.com/devanfer02/telnetquiz/tree/main/.claude/skills/xml-to-compose-migration
Command: npx skills add https://github.com/devanfer02/telnetquiz --skill xml-to-compose-migration-devanfer02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps Android developers migrate from XML-based layouts to Jetpack Compose, preserving behavior while modernizing UI code.

Core Features & Use Cases

  • Layout mapping of common XML containers (ConstraintLayout, LinearLayout, FrameLayout) to Compose equivalents.
  • State migration guidance to convert data binding/stateful patterns to Compose state and state hoisting.
  • Incremental migration strategies using interop (ComposeView and AndroidView) for gradual adoption.
  • Guidance for Include/Merge patterns, shared references, and extracting reusable components.

Quick Start

Convert the provided Android XML layout into an idiomatic Jetpack Compose version, preserving behavior, and provide an incremental migration plan.

Frequently Asked Questions about xml-to-compose-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Android XML layouts to Jetpack Compose?

To migrate Android XML layouts to Jetpack Compose, you map common XML containers like ConstraintLayout and LinearLayout to their Compose equivalents while preserving the original UI behavior.

What is the best way to handle state migration when converting data binding to Compose?

State migration from data binding involves converting stateful patterns into Compose state and applying state hoisting to ensure your UI components remain stateless and reusable.

Can I use interop patterns for incremental adoption of Jetpack Compose?

Yes, you can use interop patterns like ComposeView and AndroidView for incremental adoption, allowing you to gradually modernize complex UIs without rewriting the entire application at once.

How do I convert XML Include and Merge patterns into reusable Compose components?

Converting XML Include and Merge patterns involves extracting reusable components and resolving shared references to build idiomatic, modular Compose functions that replace the included layouts.

Does converting FrameLayout to Jetpack Compose require special handling?

Converting FrameLayout to Jetpack Compose requires mapping the container to a Box composable, which similarly stacks its children and aligns them within the parent constraints.