migrate-xml-views-to-jetpack-compose

Convert Android XML View layouts into Jetpack Compose with visual parity.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/premex-ab/claude-marketplace --skill migrate-xml-views-to-jetpack-compose-premex-ab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-xml-views-to-jetpack-compose
Source: https://github.com/premex-ab/claude-marketplace/tree/main/plugins/android-migrate-xml-views-to-jetpack-compose/skills/migrate-xml-views-to-jetpack-compose
Command: npx skills add https://github.com/premex-ab/claude-marketplace --skill migrate-xml-views-to-jetpack-compose-premex-ab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Migrating legacy Android UI from XML Views to Jetpack Compose without breaking layout, theming, or functionality.

Core Features & Use Cases

  • Step-by-step, structured migration: Follow a safe 10-step methodology from candidate selection through XML cleanup.
  • Compose dependencies, theming, and compiler setup: Ensure Compose is correctly configured and apply only the minimum required theming for the target screen/component.
  • Visual validation and parity checks: Use baseline screenshots and Compose Preview to verify pixel-consistent output, then add UI tests.

Quick Start

Use the migrate-xml-views-to-jetpack-compose skill to convert one chosen XML View layout into a pixel-consistent Jetpack Compose implementation, validate it visually, and remove the legacy XML once all usages are replaced.

Frequently Asked Questions about migrate-xml-views-to-jetpack-compose

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

FAQPage Schema
How do I migrate an Android XML layout to Jetpack Compose safely?

Migrate your XML layout to Jetpack Compose by following a 10-step workflow that includes dependency setup, minimal theming, UI conversion, and screenshot validation to ensure functional and visual parity before removing the legacy file.

Can I incrementally adopt Jetpack Compose without rewriting my entire app's theme?

Yes, you can incrementally adopt Jetpack Compose by migrating only the minimum required theming for the target screen or component, preserving interoperability with your existing XML views and avoiding a full theme rewrite.

What is the best way to validate visual parity when converting XML Views to Compose?

Validate visual parity during XML to Compose migration by comparing baseline screenshots of the legacy layout against the Compose Preview, then add UI tests to verify pixel-consistent output before replacing usages.

When should I clean up the legacy XML file after migrating to Jetpack Compose?

Clean up the legacy XML file only after you have fully migrated the UI to Jetpack Compose and replaced all existing usages of the layout, ensuring the new implementation passes visual and functional validation.

Do I need to configure Compose dependencies before converting an XML View?

Yes, you must configure Jetpack Compose dependencies and the compiler setup as part of the migration workflow before converting the XML View layout to ensure the project environment supports the new implementation.