kotlin-navigation-compose-multiplatform

Define navigation architecture for Compose Multiplatform projects using Navigation 2 semantics.

1|Updated Apr 2, 2026

Search Tags:#architecture #routing #navigation #kotlin #navcontroller #compose-multiplatform

Ready to run

npx skills add https://github.com/leogallego/ansible-jane --skill kotlin-navigation-compose-multiplatform-leogallego

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kotlin-navigation-compose-multiplatform
Source: https://github.com/leogallego/ansible-jane/tree/main/skills/kotlin-navigation-compose-multiplatform
Command: npx skills add https://github.com/leogallego/ansible-jane --skill kotlin-navigation-compose-multiplatform-leogallego

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compose Multiplatform projects often struggle with inconsistent navigation design across targets, unclear route ownership, and brittle back-stack management. This skill provides guidelines to model routes, own NavController, and coordinate navigation state for Android, iOS, and web targets.

Core Features & Use Cases

Clarifies route modeling, destination identity, and argument discipline to reduce hard-coded strings.
Defines ownership of navigation state and reduces boilerplate across leaf composables.
Supports adaptive navigation chrome and multiplatform routing decisions for consistent UX.

Quick Start

Audit the app's navigation module and adopt a single NavController owner with typed routes.

Frequently Asked Questions about kotlin-navigation-compose-multiplatform

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

FAQPage Schema

How do I structure Compose Multiplatform navigation across Android and web targets?▼

Compose Multiplatform navigation requires a single NavController owner and typed route definitions to ensure consistent routing and back-stack management across Android and web targets. Centralizing navigation state reduces brittle destination identity and hard-coded strings.

What is the best way to manage NavController ownership in Kotlin Multiplatform projects?▼

Managing NavController ownership in Kotlin Multiplatform involves hoisting navigation state to a single owner, which reduces boilerplate across leaf composables. This approach clarifies destination identity and enforces argument discipline using stable Navigation 2 semantics.

How do I model routes and arguments in Compose Multiplatform to avoid hard-coded strings?▼

Modeling routes in Compose Multiplatform involves defining typed route structures and enforcing argument discipline. This reduces hard-coded strings and clarifies destination identity, ensuring robust back-stack shaping and deep-link handling across targets.

Can I use adaptive navigation chrome for Compose Multiplatform routing decisions?▼

Adaptive navigation chrome is supported for Compose Multiplatform routing decisions to maintain consistent UX. The skill provides guidelines for coordinating multiplatform routing and adaptive UI layouts across Android and web targets.

How do I handle deep-linking and back-stack shaping in Kotlin Multiplatform navigation?▼

Deep-linking and back-stack shaping in Kotlin Multiplatform navigation are handled using stable Navigation 2 semantics. The skill specifies guidance on route definitions and state hoisting to coordinate deep-link handling and testability across platforms.