Xml To Compose
Migrate legacy Android XML screens to Jetpack Compose composables with correct attribute, style, and resource mapping.
Overview
Xml-to-compose is an agent skill for the Build phase that converts Android XML layouts into Jetpack Compose composables including styles and resource references.
Install
npx skills add https://github.com/singhsume123/xml-to-compose-skill --skill SKILL.mdWhat is this skill?
- Translates Android XML layouts into idiomatic Jetpack Compose structure
- Maps views, attributes, styles, and theme resources to Compose equivalents
- Handles common widgets and nested layout patterns from legacy XML
- Supports incremental screen-by-screen migration rather than one-shot guesses
- Focused on migration fidelity and Compose best practices, not greenfield-only snippets
Adoption & trust: 15 GitHub stars.
What problem does it solve?
Your Android app still uses XML layouts and you need accurate Compose translations without losing attributes, themes, or nested widget behavior.
Who is it for?
Indie Android apps mid-migration from View/XML to Compose with real layout and resource files in the repo.
Skip if: Greenfield Compose-only apps with no XML, iOS/SwiftUI work, or backend/API tasks.
When should I use this skill?
Asked to migrate XML layouts, convert views to composables, or help with Android Compose migration including layouts, widgets, attributes, styles, and resource references.
What do I get? / Deliverables
You get Compose composables and migration notes that mirror the original XML structure so you can delete XML screens incrementally and run UI tests on the new surfaces.
- Compose composable source replacing or paralleling target XML layouts
- Notes on attribute, style, and resource reference mapping
- Incremental migration steps per screen or module
Recommended Skills
Journey fit
How it compares
Layout migration specialist—not a general Android architecture or Play Store ASO skill.
Common Questions / FAQ
Who is xml-to-compose for?
Android developers and solo builders maintaining legacy XML UIs who want agent-assisted, screen-level Jetpack Compose conversion.
When should I use xml-to-compose?
During Build/frontend when migrating XML layouts, converting views to composables, or unblocking a Compose rollout while XML resources still exist in modules.
Is xml-to-compose safe to install?
It guides code transformation in your project; review diffs for accessibility and behavior, and use the Security Audits panel on this Prism page before wide agent auto-apply.
SKILL.md
READMESKILL.md - 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. # xml-to-compose { "name": "xml-to-compose", "description": "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." }