What is the primary purpose of the screen2navkey skill?

It is designed to automate the refactoring process of moving from the Voyager navigation library to AndroidX Navigation3 in Kotlin and Compose Multiplatform projects.

Does it handle screens with arguments?

Yes, if a screen has parameters, the skill will generate a data class NavKey to hold those parameters and pass them to the corresponding Composable.

What are the safety limitations of this skill?

The skill is strictly forbidden from modifying screens with nested navigators, already migrated pages, or navigationResult logic to ensure stability.

Will it break my existing ViewModel logic?

No, the skill is configured to preserve existing ViewModel injection patterns, such as koinViewModel, during the conversion process.

Voyager to Navigation3 Migrator

Name: Voyager to Navigation3 Migrator
Author: 0xZhangKe

by0xZhangKe

•

335

•

Mobile Development

Automates the migration of Voyager Screens to AndroidX Navigation3 patterns in Kotlin Multiplatform projects.

This skill facilitates the transition from the Voyager navigation framework to AndroidX Navigation3 (navigation3-runtime). It identifies legacy Voyager screens, converts them into type-safe NavKeys and standalone Composable functions, and automatically registers these components within the project's NavEntryProvider. Designed for Jetpack Compose and Kotlin Multiplatform environments, it handles both static and parameterized screens while ensuring dependency injection patterns like Koin remain intact. It follows a strict safety protocol by skipping nested navigators and preserving existing navigation logic to ensure a stable refactoring process.

Key Features

01Safe refactoring that preserves Koin ViewModel injections and navigation results

02Automated conversion of Voyager Screen classes to Navigation3 NavKeys

03335 GitHub stars

04Smart parameter mapping for data class NavKey generation

05Generation of standalone @Composable functions from class-based screens

06Automatic registration of new keys in the module's NavEntryProvider

Use Cases

01Modernizing Kotlin Multiplatform app architecture from legacy navigation frameworks

02Standardizing navigation patterns across multiple feature modules in large-scale apps

03Refactoring Compose Multiplatform UI to adopt the latest AndroidX Navigation standards

Key Features

01Safe refactoring that preserves Koin ViewModel injections and navigation results

02Automated conversion of Voyager Screen classes to Navigation3 NavKeys

03335 GitHub stars

04Smart parameter mapping for data class NavKey generation

05Generation of standalone @Composable functions from class-based screens

06Automatic registration of new keys in the module's NavEntryProvider

Use Cases

01Modernizing Kotlin Multiplatform app architecture from legacy navigation frameworks

02Standardizing navigation patterns across multiple feature modules in large-scale apps

03Refactoring Compose Multiplatform UI to adopt the latest AndroidX Navigation standards