android-navigation
Type-safe Compose Navigation for Android/KMP - route objects, feature nav graphs, cross-feature callbacks, and wiring in :app. Use this skill whenever setting up navigation, defining routes, adding a new screen to a nav graph, navigating between features, or wiring nav graphs in the app module. Trigger on phrases like "set up navigation", "add a route", "navigate between screens", "nav graph", "NavController", "type-safe nav", "cross-feature navigation", or "NavGraphBuilder".
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.4k
- Forks
- 82
01 前言 Front Matter
- name
- android-navigation
- description
- Type-safe Compose Navigation for Android/KMP - route objects, feature nav graphs, cross-feature callbacks, and wiring in :app. Use this skill whenever setting up navigation, defining routes, adding a new screen to a nav graph, navigating between features, or wiring nav graphs in the app module. Trigger on phrases like "set up navigation", "add a route", "navigate between screens", "nav graph", "NavController", "type-safe nav", "cross-feature navigation", or "NavGraphBuilder".
03 SKILL.md 正文
Android / KMP Navigation
Principles
- Type-safe navigation with
@Serializableroute objects (KotlinX Serialization). - One nav graph per feature, defined in the feature's
presentationmodule. - Feature nav graphs are assembled in
:app. - Navigation within a feature uses a
NavControllerpassed into the feature nav graph. - Feature-to-feature navigation uses callbacks, keeping features decoupled.
Route Objects
Define routes as @Serializable objects or data classes in the feature's presentation module:
// feature:notes:presentation
@Serializable object NoteListRoute
@Serializable data class NoteDetailRoute(val noteId: String)
Use data object for screens with no parameters, data class for screens with arguments.
Feature Nav Graph
Each feature exposes a NavGraphBuilder extension function:
// feature:notes:presentation
fun NavGraphBuilder.notesGraph(
navController: NavController,
onNavigateToEditor: (String) -> Unit // callback for cross-feature navigation
) {
navigation<NoteListRoute>(startDestination = NoteListRoute) {
composable<NoteListRoute> {
NoteListRoot(
onNavigateToDetail = { navController.navigate(NoteDetailRoute(it)) }
)
}
composable<NoteDetailRoute> { backStackEntry ->
val route: NoteDetailRoute = backStackEntry.toRoute()
NoteDetailRoot(
noteId = route.noteId,
onNavigateToEditor = onNavigateToEditor
)
}
}
}
Wiring in :app
All feature nav graphs are assembled in one place:
// :app
NavHost(navController, startDestination = NoteListRoute) {
notesGraph(
navController = navController,
onNavigateToEditor = { navController.navigate(EditorRoute(it)) }
)
editorGraph(navController)
}
Cross-feature navigation is always expressed as a lambda callback — never by importing a route from another feature module.
Passing Arguments
For simple scalar arguments, use @Serializable data class routes:
@Serializable data class NoteDetailRoute(val noteId: String)
// Navigate
navController.navigate(NoteDetailRoute(noteId = "abc123"))
// Receive
composable<NoteDetailRoute> { backStackEntry ->
val route: NoteDetailRoute = backStackEntry.toRoute()
// route.noteId available here
}
Avoid passing complex objects via navigation — pass IDs and load data in the destination ViewModel.
Naming Conventions
| Thing | Convention | Example |
|---|---|---|
| Nav route | <Screen>Route |
NoteListRoute, NoteDetailRoute |
| Feature nav graph | <feature>Graph(...) on NavGraphBuilder |
notesGraph(...) |
Checklist: Adding Navigation to a New Feature
- [ ] Define
@Serializableroute objects for each screen infeature:presentation - [ ] Add feature nav graph function (
NavGraphBuilder.<feature>Graph(...)) - [ ] Pass
NavControllerfor intra-feature navigation - [ ] Expose cross-feature destinations as lambda callbacks (not direct route imports)
- [ ] Wire nav graph and cross-feature callbacks in
:app'sNavHost
04 同仓库更多 Skills
review-animations
Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.
prototype
Build multiple genuinely different versions of a UI piece you describe, rendered behind a visual picker so you can flip through them live and promote the one that feels right. Only runs when explicitly invoked; it does not trigger on its own.
pick-ui-library
Pick the right library for a given frontend task from a curated, opinionated list — numbers, OTP inputs, charts, command menus, virtualization, drag and drop, toasts, state, styling, and more. Only runs when explicitly invoked; it does not trigger on its own.
improve-animations
Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.
grilling
Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
grill-with-docs
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.