kmp-navigation

Implement cross-platform navigation patterns in Kotlin Multiplatform projects with Voyager and Decompose examples.

61|17|Updated Feb 2, 2026

Search Tags:#navigation #swiftui #navigate #compose #decompose #kmp #voyager

Ready to run

npx skills add https://github.com/ahmed3elshaer/everything-claude-code-mobile --skill kmp-navigation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kmp-navigation
Source: https://github.com/ahmed3elshaer/everything-claude-code-mobile/tree/main/skills/kmp-navigation
Command: npx skills add https://github.com/ahmed3elshaer/everything-claude-code-mobile --skill kmp-navigation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-platform navigation is challenging in Kotlin Multiplatform projects; this Skill provides unified strategies and patterns to implement navigation across Android, iOS, and shared code.

Core Features & Use Cases

Voyager-based navigation across Android, iOS, and shared code with platform adapters for Compose Navigation and SwiftUI.
Decompose-style navigation patterns to manage state and configuration across modules.
Platform-native bridging guidance for implementing consistent navigation flows on target platforms.

Quick Start

Install and configure the navigation patterns in your KMP project, then integrate Voyager, Decompose, or platform-native approaches as shown in the examples.

Frequently Asked Questions about kmp-navigation

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

FAQPage Schema

How do I implement navigation across Android and iOS in a Kotlin Multiplatform project?▼

Cross-platform navigation in KMP uses shared code patterns bridged to platform-specific implementations. This Skill covers Voyager for unified navigation, Decompose for state management, and platform-native adapters that connect to Compose Navigation on Android and SwiftUI on iOS, with concrete integration examples.

What's the best way to set up Voyager navigation in a KMP project?▼

Voyager provides library dependencies and build configuration to enable navigation across Android, iOS, and shared code. This Skill specifies integration steps, required dependencies, and sample navigational code patterns to implement common flows in your KMP setup.

Can I use Decompose for state management across KMP modules?▼

Yes. Decompose manages state and configuration across modules in Kotlin Multiplatform projects. This Skill explains Decompose-style navigation patterns, how they differ from library-based approaches, and when to apply them alongside Voyager or platform-native strategies.

How do platform-native navigation patterns integrate with shared KMP code?▼

Platform-native bridging connects shared navigation logic to Compose Navigation on Android and SwiftUI on iOS. This Skill provides guidance on implementing consistent navigation flows by adapting shared patterns to each platform's native navigation system.

What are the differences between Voyager and Decompose for KMP navigation?▼

Voyager offers library-driven navigation across platforms with built-in adapters, while Decompose emphasizes state and configuration management across modules. This Skill covers both approaches, their trade-offs, and how to choose based on your project's architecture needs.

Do I need both Compose Navigation and SwiftUI expertise to implement cross-platform navigation?▼

No. This Skill bridges the gap by providing platform adapters and integration patterns that abstract platform-specific details. You define navigation in shared code or Voyager, then adapt it to Compose Navigation and SwiftUI using the patterns and examples included.