migrate-to-compose

Plan end-to-end Android UI migration from Views to Jetpack Compose.

23|2|Updated Mar 7, 2026

Search Tags:#ui #architecture #verification #migration #android #compose

Ready to run

npx skills add https://github.com/kirich1409/krozov-ai-tools --skill migrate-to-compose

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrate-to-compose
Source: https://github.com/kirich1409/krozov-ai-tools/tree/main/plugins/developer-workflow-kotlin/skills/migrate-to-compose
Command: npx skills add https://github.com/kirich1409/krozov-ai-tools --skill migrate-to-compose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill guides teams through structured migration of Android UI from traditional View-based screens to Jetpack Compose, ensuring consistent behavior, visual fidelity, and a repeatable workflow.

Core Features & Use Cases

Phase-driven migration from Activity/Fragment/Custom View to Compose, including discovery, pattern analysis, gap analysis, confirmation, implementation, static verification, and API audits.
Generates artifacts such as behavior-scenarios, migration reports, and clear plan for ViewModel/state adjustments.
Supports risk assessment and scaffolding for custom views migrating to Compose with recommended approaches and toolchain references.

Quick Start

Provide a screen migration plan to convert a Fragment screen to a Compose-based screen; specify source type, state shape, and navigation approach.

Frequently Asked Questions about migrate-to-compose

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

FAQPage Schema

How do I plan an Android UI migration from Views to Jetpack Compose?▼

To plan an Android UI migration from Views to Jetpack Compose, you need a phase-driven workflow covering discovery, gap analysis, strategy, and verification. This approach generates artifacts like behavior scenarios and migration reports to ensure visual fidelity and consistent behavior.

What is the best way to migrate a Fragment screen to Compose?▼

The best way to migrate a Fragment screen to Compose is applying a structured end-to-end migration plan. This includes analyzing source types, adjusting ViewModel state shapes, defining navigation approaches, and performing static verification to confirm behavioral consistency.

Does Compose migration support custom Views and Activities?▼

Yes, Compose migration supports custom Views and Activities. The process includes detailed discovery, risk assessment, and scaffolding for custom views, alongside specific pattern analysis and View API audits to ensure all View-based components are successfully converted.

How do I verify behavior consistency after migrating Android UI to Compose?▼

You verify behavior consistency after migrating Android UI to Compose by generating behavior-scenarios and conducting static verification. A dedicated View API audit and migration report explicitly handle risks and confirm that the new Compose UI matches the original View-based screen.

What artifacts are generated during an Android UI to Compose migration?▼

Artifacts generated during an Android UI to Compose migration include behavior-scenarios, a detailed migration report, and a clear plan for ViewModel and state adjustments. These outputs enforce migration constraints and document explicit risk handling across all phases.

When should I not use a structured phase-driven workflow for Compose migration?▼

You might bypass a structured phase-driven workflow for Compose migration if your screen lacks complex state logic or custom Views. However, for comprehensive gap analysis, API audits, and explicit risk handling, a guided phase-driven approach is necessary to maintain visual fidelity.