Compose Multiplatform Navigation

Use this skill when designing, implementing, or reviewing navigation in a Compose Multiplatform project.

This skill is intentionally strict. Its purpose is to keep route modeling coherent, back stack behavior explicit, argument passing minimal, navigation side effects controlled, and multiplatform routing boundaries clean across Android and shared Compose code.

Navigation library scope: This skill covers Jetpack Navigation 2 and its Compose Multiplatform equivalent (navigation-compose / NavHost / NavController) — still the default for many existing KMP apps. Navigation 3 is stable on Android; Compose Multiplatform ships multiplatform Navigation 3 artifacts (verify current alpha/stable labels in JetBrains release notes before migrating). Nav3 uses a different back-stack model (NavDisplay / NavEntry). If the project uses Navigation 3, verify which guidance applies. Docs: https://developer.android.com/guide/navigation/navigation3 · https://kotlinlang.org/docs/multiplatform/compose-navigation-3.html

Primary goals

The navigation design should optimize for: