Android Navigation Standards
SkillAI & modelsImplement type-safe Jetpack Navigation Compose routes using Kotlin serialization. Use only when defining typed Compose destinations and arguments; defer XML navigation, deep links, animations, and generic auth or bottom-navigation work.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Android Navigation Standards skill
What this skill tells your AI
The instructions your AI receives, as published by hoangnguyen0403/agent-skills-standard in skills/android/android-navigation-type-safe/SKILL.md and read by ahel’s review.
Priority: P0 (CRITICAL)
Implementation Guidelines
Type-Safe Navigation
- Library: Navigation Compose 2.8.0+.
- Routes: Use
@Serializableobjects/classes instead of String routes. - Arguments: No manual bundle parsing. Use
.toRoute<T>().
Structure
- Graphs: Split large apps into nested navigation graphs (
navigationextension functions). - Hoisting: Hoist navigation events out of Screens. Composable screens should accept callbacks (
onNavigateToX).
Anti-Patterns
- No String Routes: Use @Serializable typed objects/classes for destinations.
- No NavController in Composables: Hoist navigation events to screen-level callbacks.
References
Required route example
- For a product detail argument, define
@Serializable data class ProductDetail(val productId: Long)and navigate with the typed destination; retrieve it withtoRoute<ProductDetail>().
Canonical response anchors
When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
- Define ProductDetail(val productId
Signals
- GitHub stars
- 565
- Forks
- 164
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
android-navigation-type-safe- Source
- github.com/hoangnguyen0403/agent-skills-standard