android-navigation-type-safe
Implement type-safe Jetpack Navigation Compose routes on Android. Use when implementing type-safe navigation graphs in Jetpack Compose for Android. (triggers: **/*NavHost.kt, **/*Graph.kt, NavHost, navController, @Serializable)
85
Quality
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Securityby
Passed
No known issues
Android Navigation Standards
Priority: P0
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
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- Last updated
- Created
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.