kmp-migration

When to Use This Skill

Use when:

• An existing Android or KMP project needs to adopt the 6-layer architecture incrementally
• A team is migrating from MVVM+LiveData to MVI+StateFlow screen by screen
• You need to split a monolithic module into :presenter / :ui without breaking everything
• You want a prioritized order for adopting skills in a project that has none yet

Freshness rule: migration paths reference specific skills (MVI, clean-architecture, DI). Recheck those skills for updated patterns before executing a migration step — the target pattern may have changed since this skill was written.

Trigger keywords: migrate existing project, adopt MVI, LiveData to StateFlow, migrate to clean architecture, incremental adoption, where to start, existing project, brownfield, refactor architecture, add layers to project, how to adopt skills, migration path, legacy project, retrofit architecture, migrate ViewModel.