Agent skill

Android Compose Migration

by HoangNguyen0403 in HoangNguyen0403/agent-skills-standard

Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow.

MITAuto-check passedMobile

Install Android Compose Migration

skills CLI
$ npx skills add HoangNguyen0403/agent-skills-standard --skill android-compose-migration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HoangNguyen0403/agent-skills-standard android-compose-migration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/android/android-compose-migration .claude/skills/android-compose-migration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
android-compose-migration
GitHub stars
572
Token cost
~767 tokens
SKILL.md length
335 words
Files
4 (incl. references)
Skills in repo
211
Repo updated
First seen
Licence
MIT

At a glance

Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow.

  • Works in 10 steps: Identify the migration candidate → Analyze the layout → Create a plan → …
  • Converting XML layouts to Compose
  • SKILL.md covers Priority: P1 (HIGH), Step 1: Identify the migration…, Step 2: Analyze the layout and Step 3: Create a plan, plus 10 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Android Compose Migration is an agent skill from HoangNguyen0403/agent-skills-standard. Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.

Its SKILL.md is about 770 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `evals/evals.json`, `references/dependency-setup.md` and `references/interop-patterns.md`).

It sits in Mobile, covering Android development. It works with Android and Jetpack Compose. The repository describes itself as: A collection of Agent Skills Standard and Best Practice for Programming Languages, Frameworks that help our AI Agent follow best practies on frameworks and programming laguages. The licence is MIT.

When your agent uses it

  • Converting XML layouts to Compose
  • Setting up Compose in an existing View-based project
  • Incrementally adopting Compose

Example prompts

  • “/android-compose-migration”

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Identify the migration candidate
  2. Analyze the layout
  3. Create a plan
  4. Capture baseline UI
  5. Set up Compose dependencies
  6. Set up Compose theming
  7. Migrate the XML layout
  8. Replace usages
  9. Validate
  10. Clean up

What it can do on your machine

Read from SKILL.md and the folder at commit b529c2d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Android Compose Migration loads about 767 tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 62 tokens; SKILL.md has 335 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~767
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from HoangNguyen0403/agent-skills-standard at commit b529c2d, republished under its MIT licence (© HoangNguyen0403). 335 words, ~767 tokens.

Download SKILL.mdSave it as .claude/skills/android-compose-migration/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
android-compose-migration
description
Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.

XML to Jetpack Compose Migration

Priority: P1 (HIGH)

Structured 10-step workflow for migrating XML layouts to Compose.

Step 1: Identify the migration candidate

If the user specified a target XML layout, proceed to Step 2. Otherwise, pick the best candidate:

  • Prefer leaf layouts (not deeply nested in other XMLs).
  • Prefer layouts with few custom Views.
  • Avoid layouts with complex RecyclerView adapters as a first migration.

Step 2: Analyze the layout

Examine the XML structure: list all Views, data bindings, click listeners, style references, and custom Views needing AndroidView wrappers.

Step 3: Create a plan

Generate a checklist of every View → Composable mapping. Present to user for approval.

Step 4: Capture baseline UI

Ask the user for a screenshot, or take one via emulator for visual comparison.

Step 5: Set up Compose dependencies

Check build.gradle.kts or libs.versions.toml for Compose BOM and compiler. If missing, add them. See dependency setup.

Step 6: Set up Compose theming

If missing, initialize minimum required theme — map XML colors/styles to Compose. Do NOT migrate the entire theme.

Step 7: Migrate the XML layout

Convert each View to its Compose equivalent. See interop patterns for the View→Composable mapping table, ComposeView, and AndroidView usage. Include a @Preview for every new Composable. Use LazyColumn or LazyRow for list-heavy screens instead of flattening them into one large static composable.

Step 8: Replace usages

Use ComposeView to host Compose in Views, or AndroidView for Views in Compose. See interop patterns.

Step 9: Validate

Compare baseline screenshot with Compose Preview. Focus on layout and styling. Iterate until visual parity.

Step 10: Clean up

Delete the migrated XML file and legacy tests. Only remove code not referenced elsewhere.

Verification

  • Compose Preview renders correctly.
  • Visual parity with original XML layout.
  • ./gradlew build succeeds.
  • No broken references to deleted XML files.

Anti-Patterns

  • No full theme migration: Only migrate what the target layout needs.
  • No new View instances in AndroidView update: Mutate existing, don't recreate.
  • No missing ViewCompositionStrategy: Always set it on ComposeView to avoid leaks.

References

© HoangNguyen0403, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/android/android-compose-migration of HoangNguyen0403/agent-skills-standard.

  • SKILL.md
  • evals/evals.json
  • references/dependency-setup.md
  • references/interop-patterns.md

Open the folder on GitHubat commit b529c2d

Compare with similar skills

Android Compose Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Android Compose Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Android Compose Migration this skillHoangNguyen0403/agent-skills-standard572—~767Automated safety check: PassMIT
Compose Multiplatform Patternsmonta-app/ocpp-emulator1805 repos~2kAutomated safety check: PassApache-2.0
Android Developmentdpconde/claude-android-skill336—~1.7kAutomated safety check: PassMIT
Benchmarkandroidx/androidx6.1k—~1.1kAutomated safety check: PassApache-2.0
Mobile Android Designopenvetta/open-vetta2903 repos~950Automated safety check: PassApache-2.0
Stylessreichholf/dreamDroid1165 repos~2.3kAutomated safety check: PassGPL-3.0

Similar skills

  • Compose Multiplatform Patterns

    monta-app/ocpp-emulator

    Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.

    180 GitHub starsUsed in 5 repos~2k tokens
    MobileAuto-check passed
  • Android Development

    dpconde/claude-android-skill

    Create production-quality Android applications following Google's official architecture guidance and NowInAndroid best practices.

    336 GitHub stars~1.7k tokensUpdated 10 mo ago
    MobileAuto-check passed
  • Benchmark

    androidx/androidx

    Benchmarking and improving the performance of Jetpack Compose.

    6.1k GitHub stars~1.1k tokensUpdated yesterday
    MobileAuto-check passed
  • Mobile Android Design

    openvetta/open-vetta

    Master Material Design 3 and Jetpack Compose patterns for building native Android apps.

    290 GitHub starsUsed in 3 repos~950 tokens
    MobileAuto-check passed
  • Styles

    sreichholf/dreamDroid

    A skill your agent uses to integrate the Jetpack Compose Styles API into an Android project.

    116 GitHub starsUsed in 5 repos~2.3k tokens
    MobileAuto-check passed
  • Generating Baseline Profiles

    rosuH/EasyWatermark

    A skill your agent uses to generate and measure Jetpack Compose Baseline Profiles end-to-end with the AGP 8.2+ Baseline Profile Generator module and the Macrobenchmark harness.

    1.9k GitHub starsUsed in 1 repo~5k tokens
    MobileAuto-check passed

More from HoangNguyen0403/agent-skills-standard

All 211 skills in this repo
  • Subagent-Driven Development

    HoangNguyen0403/agent-skills-standard

    Runs a multi-task implementation plan by sending each task to a fresh implementer subagent, reviewing it independently, then reviewing the whole branch.

    572 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • draw.io Architecture Diagramming

    HoangNguyen0403/agent-skills-standard

    Draws architecture diagrams as editable draw.io files from a JSON spec, with a fixed house style, one C4 level per diagram and evidence-tagged shapes.

    572 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Android Navigation 3 Guide

    HoangNguyen0403/agent-skills-standard

    Implements and migrates to Jetpack Navigation 3 in Compose: NavDisplay, typed route objects, a state-list back stack, deep links, multiple back stacks and dialog scenes.

    572 GitHub stars~687 tokensUpdated yesterday
    Auto-check passed
  • Angular HttpClient Standards

    HoangNguyen0403/agent-skills-standard

    Sets rules for Angular HTTP code: functional interceptors, typed requests, services that own every call, and httpResource for reactive data loading in Angular 17+.

    572 GitHub stars~652 tokensUpdated yesterday
    Auto-check passed
  • Angular Tooling

    HoangNguyen0403/agent-skills-standard

    Angular CLI usage, code generation, build configuration, and bundle optimization.

    572 GitHub stars~743 tokensUpdated yesterday
    Auto-check passed
  • Common Code Review

    HoangNguyen0403/agent-skills-standard

    Conduct high-quality, persona-driven code reviews. An agent skill from HoangNguyen0403/agent-skills-standard.

    572 GitHub stars~772 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Android Compose Migration

What does Android Compose Migration do?

Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Android Compose Migration is an agent skill from HoangNguyen0403/agent-skills-standard. Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow.

When should I use Android Compose Migration?

Android Compose Migration fits situations like: converting XML layouts to Compose; setting up Compose in an existing View-based project; incrementally adopting Compose.

How do I install Android Compose Migration in Claude Code?

Run `npx skills add HoangNguyen0403/agent-skills-standard --skill android-compose-migration -a claude-code`. Or copy the skill folder (skills/android/android-compose-migration in HoangNguyen0403/agent-skills-standard) into .claude/skills/android-compose-migration in your project. Claude Code loads it when a task matches its description.

How do I install Android Compose Migration in Codex?

Run `npx skills add HoangNguyen0403/agent-skills-standard --skill android-compose-migration -a codex`. Or copy the skill folder (skills/android/android-compose-migration in HoangNguyen0403/agent-skills-standard) into .agents/skills/android-compose-migration in your project. Codex loads it when a task matches its description.

Can I use Android Compose Migration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HoangNguyen0403/agent-skills-standard --skill android-compose-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/android-compose-migration, .gemini/skills/android-compose-migration, .github/skills/android-compose-migration and .opencode/skills/android-compose-migration in your project.

What does Android Compose Migration need to run?

SKILL.md names no scripts, command-line tools or credentials: Android Compose Migration is instructions for the agent only.

Does Android Compose Migration access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Android Compose Migration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Android Compose Migration use?

Android Compose Migration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Android Compose Migration use?

About 767 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 978 tokens, read only when the agent opens those files.

What are the alternatives to Android Compose Migration?

Skills that share tags, products or a category with Android Compose Migration: Compose Multiplatform Patterns (monta-app/ocpp-emulator, 180 stars), Android Development (dpconde/claude-android-skill, 336 stars), Benchmark (androidx/androidx, 6.1k stars) and Mobile Android Design (openvetta/open-vetta, 290 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Android Compose Migration?

HoangNguyen0403 (a GitHub user) maintains it in HoangNguyen0403/agent-skills-standard, which has 572 GitHub stars. The repository holds 211 skills in this directory. The repository was last updated on October 9, 2026.

Source: HoangNguyen0403/agent-skills-standard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.