Back to skills
SKILL.md
Android Navigation Type Safe
ASecurityStandards for Jetpack Navigation Compose (Type-safe). Use when implementing type-safe navigation graphs in Jetpack Compose for Android. (triggers: **/*NavHost.kt, **/*Graph.kt, NavHost, navController, @Serializable)
- 43 stars
- 0 votes
- 0 copies
- 1 view
- Added May 30, 2026
Security analysis
100/100npx -y skills add ComeOnOliver/skillshub --skill android-navigation-type-safe --agent claude-codeAre you the author of Android Navigation Type Safe?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/comeonoliver-android-navigation-type-safe)---
name: android-navigation-type-safe
description: "Standards for Jetpack Navigation Compose (Type-safe). Use when implementing type-safe navigation graphs in Jetpack Compose for Android. (triggers: **/*NavHost.kt, **/*Graph.kt, NavHost, navController, @Serializable)"
---
# Android Navigation Standards
## **Priority: P0**
## Implementation Guidelines
### Type-Safe Navigation
- **Library**: Navigation Compose 2.8.0+.
- **Routes**: Use `@Serializable` objects/classes instead of String routes.
- **Arguments**: No manual bundle parsing. Use `.toRoute<T>()`.
### Structure
- **Graphs**: Split large apps into nested navigation graphs (`navigation` extension 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
- [Route Definitions](references/implementation.md)
Attribution
Comments
Loading comments…