android-navigation

Define type-safe navigation routes with KotlinX Serialization for Android/KMP Compose apps.

Updated Apr 14, 2026

Search Tags:#navigation #mobile #android #kotlin #type-safe #compose #kmp

Ready to run

npx skills add https://github.com/kvithayathil/agent-resources --skill android-navigation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: android-navigation
Source: https://github.com/kvithayathil/agent-resources/tree/main/skills/android/android-navigation
Command: npx skills add https://github.com/kvithayathil/agent-resources --skill android-navigation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of runtime navigation crashes and tightly coupled feature modules in Android/KMP Compose apps caused by untyped route arguments and direct cross-feature route dependencies.

Core Features & Use Cases

Type-safe route definitions: Use @Serializable objects to define navigation routes, eliminating runtime errors from incorrect argument passing.
Modular feature nav graphs: Organize navigation per feature module to keep codebases maintainable and scalable.
Decoupled cross-feature navigation: Use lambda callbacks instead of direct route imports to avoid tight coupling between feature modules.
Use Case: For a multi-module Android/KMP app with notes and editor features, use this Skill to implement type-safe navigation between screens without creating direct dependencies between the feature modules.

Quick Start

Use the android-navigation skill to set up type-safe navigation for your Android/KMP Compose app's note list, detail, and editor screens.

Frequently Asked Questions about android-navigation

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

FAQPage Schema

How do I prevent runtime crashes in Android Compose navigation?▼

Type-safe Android Compose navigation prevents runtime crashes by using @Serializable objects for route definitions. This eliminates errors from incorrect argument passing and removes untyped string routes.

What's the best way to decouple cross-feature navigation in a multi-module Android app?▼

Decoupling cross-feature navigation in a multi-module Android app is best achieved using lambda callbacks. This prevents tight inter-module coupling by avoiding direct route imports between feature modules during screen transitions.

How do I set up type-safe navigation in a KMP Compose project?▼

Setting up type-safe navigation in a KMP Compose project involves using KotlinX Serialization with NavController to define modular per-feature navigation graphs. This architecture ensures maintainable and scalable route management.

Does this type-safe navigation approach work with Kotlin Multiplatform?▼

Yes, this type-safe navigation approach works with Kotlin Multiplatform. It supports KMP Compose applications by applying modular per-feature navigation graphs and decoupled cross-feature screen transitions across shared modules.

Why does my Android Compose app have tightly coupled feature modules?▼

Tightly coupled feature modules in Android Compose apps are caused by direct cross-feature route dependencies and untyped route arguments. Replacing direct imports with lambda callbacks eliminates this tight inter-module coupling.