What is migrate-xml-views-to-jetpack-compose?

A structured workflow for replacing one Android XML layout, the older text-based way to describe screens, with Jetpack Compose, Android's newer code-based UI toolkit.

Use it to plan, convert, validate, replace usages of, and clean up a selected XML View layout.

It provides a controlled migration path while aiming to preserve the existing screen's appearance and behavior before removing the old XML.

migrate-xml-views-to-jetpack-compose — Skill for Claude Code by hanami

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add hanamizuki/solopreneur --skill migrate-xml-views-to-jetpack-compose

Clone the repo

git clone --depth 1 https://github.com/hanamizuki/solopreneur

Made for: Claude Code.

Or install android-dev, the plugin that ships this one along with the rest of its 36 skills, 1 agent.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/hanamizuki/solopreneur/migrate-xml-views-to-jetpack-compose/github.svg)](https://agentmods.dev/skills/hanamizuki/solopreneur/migrate-xml-views-to-jetpack-compose)

Your own site

<a href="https://agentmods.dev/skills/hanamizuki/solopreneur/migrate-xml-views-to-jetpack-compose"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/migrate-xml-views-to-jetpack-compose/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hanamizuki/solopreneur/migrate-xml-views-to-jetpack-compose"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/migrate-xml-views-to-jetpack-compose.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,157 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 97% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00098	$0.01157
Opus 5	$0.00049	$0.00579
Sonnet 5	$0.00020	$0.00231
Haiku 4.5	$0.00010	$0.00116

Measured 11d ago against content hash 24b392a9fccb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

migrate-xml-views-to-jetpack-compose scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

97% identical to migrate-xml-views-to-jetpack-compose — 63 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/claude/android-dev/skills/migrate-xml-views-to-jetpack-compose/SKILL.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

This skill guides through the process of migrating an existing Android XML View to Jetpack Compose. It performs a stable, safe and visually consistent transition by following a structured, 10-step methodology. This skill migrates UI (XML to Jetpack Compose) only.

Objective

To systematically convert a single legacy XML layout into modern, declarative Jetpack Compose UI while maintaining pixel-perfect visual parity and functional integrity.

Summary of the 10-step migration process

Identify the optimal XML candidate for migration
Analyze the project and layout
Create a plan
Capture the XML View UI
Set up Compose dependencies and compiler
Set up Compose theming
Migrate the XML layout to Compose
Validate the migration
Replace usages
XML code removal

Detailed steps

Step 1: Identify the optimal XML candidate for migration

If the user has explicitly specified a target XML layout, proceed to Step 2. Otherwise, analyze the codebase to identify the best candidate for migration by following the logic in references/identify-optimal-xml-candidate.md.

Step 2: Analyze the project and layout

Analyze the identified XML View's structure, hierarchy, and implementation details. Use references/analysis-of-the-project-and-layout.md to guide your technical audit of the layout and surrounding project context.

Step 3: Create a plan

Using the outputs and analysis done in the Step 1 and 2, generate a step-by-step plan for the migration. If you support user interaction, present to the user and ask for approval before proceeding. If user interaction is not supported, proceed to Step 4 following the generated plan.

Step 4: Capture the XML View UI

IF you support user interaction, ask the user to upload a screenshot of the XML View UI or provide an absolute path to a file. Use this image as a visual reference for the layout migration in Step 7. ELSE IF you are able to run an Android emulator, locate an existing screenshot test for the XML candidate. If none exists, create one using the existing project testing framework. If no framework exists, use UI Automator or Espresso to create a screenshot test with minimum required setup. Run the test and take a baseline screenshot of the XML UI. ELSE proceed to Step 5.

Read the full file on GitHub · 86 lines

Files

What ships with it

8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

11d ago First seen · 86 lines · 98 tokens per session scan A 24b392a9fccb

Subscribe to this mod's changes

migrate-xml-views-to-jetpack-compose is a skill published in the GitHub repository hanamizuki/solopreneur (148 stars, last pushed 26d ago), licensed MIT. It adds 98 tokens to every session and 1,157 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to migrate-xml-views-to-jetpack-compose, differing in 63 lines, and is treated as a copy.

Frontend Mobile

animate-expo

Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and…

emilkowalski/skills · 112 tokens

leanback-to-compose-tv-migration

Provides instructions and architectural patterns for migrating Android TV applications from legacy Leanback UI Toolkit, Android Views, or Support Fragments to Jetpack Compose for TV (androidx.tv). Use this skill for Leanback to Compose migrations, including browse screen, settings screen, authentication screen, login…

android/skills · 151 tokens

maui-data-binding

Guidance for .NET MAUI XAML and C# data bindings — compiled bindings, INotifyPropertyChanged / ObservableObject, value converters, binding modes, multi-binding, relative bindings, fallbacks, and MVVM best practices. USE FOR: setting up compiled bindings with x:DataType, implementing INotifyPropertyChanged or…

dotnet/skills · 180 tokens

expo-brownfield

Framework (OSS). Integrate Expo and React Native into an existing native iOS or Android app. Use for brownfield, embedding a React Native screen in SwiftUI/UIKit or Kotlin, or AAR/XCFramework packaging. Covers isolated and integrated approaches. For building or distributing a purely native app with EAS, use…

expo/skills · 74 tokens