A skill covering the main APIs in the official documentation on screen transitions in Android (Kotlin / Jetpack Compose). Navigation 3 is the current stable choice for new Compose implementations, while Navigation Compose handles existing 2.x graphs and Fragment-based navigation. Read the appropriate README.md according to the user's task, and follow it to the individual files.
Directory structure
skills/android-navigation/
SKILL.md
references/
navigation3/
README.md
navigation-3.md
navkey.md
navbackstack.md
naventry.md
entryprovider.md
navdisplay.md
navdisplay-animation.md
naventrydecorator.md
remembersaveablestateholdernaventrydecorator.md
rememberviewmodelstorenaventrydecorator.md
scene.md
scenestrategy.md
dialogscenestrategy.md
singlepanescenestrategy.md
listdetailscenestrategy.md
supportingpanescenestrategy.md
scenedecoratorstrategy.md
migration-guide.md
modularize.md
nav-compose/
README.md
navhost.md
navcontroller.md
remembernavcontroller.md
navhostcontroller.md
testnavhostcontroller.md
composable.md
navigation.md
dialog.md
type-safe-routes.md
navbackstackentry.md
navargument.md
navtype.md
navoptions.md
popbackstack.md
currentbackstackentryasstate.md
hiltviewmodel.md
localownersprovider.md
navhostfragment.md
findnavcontroller.md
navigationui.md
safe-args.md
navigation-graph-xml.md
navigation-feature-modules.md
deep-links/
README.md
deep-link-types.md
intent-filter-deep-links.md
asset-links-verification.md
verify-app-links.md
nav-deep-link.md
deep-link-xml-tag.md
handle-deep-link.md
navigation3-deep-links.md
intent-action-view-launch-mode.md
test-deep-links.md
back-navigation/
README.md
back-handler.md
predictive-back-handler.md
navigation-back-handler.md
on-back-pressed-dispatcher.md
on-back-pressed-callback.md
navigation-event-dispatcher.md
navigation-event-handler.md
navigation-event-input.md
local-on-back-pressed-dispatcher-owner.md
back-event-compat.md
on-back-invoked-dispatcher.md
on-back-invoked-callback.md
enable-on-back-invoked-callback.md
predictive-back-animations.md
custom-back-navigation.md
Exploration procedure
Derive the category from the task, and identify the target page in the category's README.md:
- Find the category corresponding to the task in the mapping table below
- For that category's
references/{category}/README.mdto identify the target page - the target page's
.mdand check the details
Task → Category Mapping
| Task | Category | Reference README |
|---|---|---|
| I want to implement screen transitions in Navigation 3 with NavDisplay / NavBackStack / NavKey | navigation3 | references/navigation3/README.md |
| I want to associate keys with content using entryProvider / NavEntry | navigation3 | references/navigation3/README.md |
| I want to compose adaptive scenes such as list-detail and supporting pane with Scene / SceneStrategy | navigation3 | references/navigation3/README.md |
| I want to implement screen transitions in Navigation Compose with NavHost / NavController / composable | nav-compose | references/nav-compose/README.md |
| I want to handle arguments and transition options with type-safe routes (Type-Safe Routes) and NavOptions / NavType | nav-compose | references/nav-compose/README.md |
| I want to implement Fragment-based navigation with NavHostFragment / Safe Args / Navigation Graph XML | nav-compose | references/nav-compose/README.md |
| I want to declare and verify deep links and App Links (intent-filter, assetlinks.json, autoVerify) | deep-links | references/deep-links/README.md |
| I want to implement transitions via Navigation with navDeepLink / handleDeepLink / NavDeepLinkBuilder | deep-links | references/deep-links/README.md |
| I want to test deep link and App Links behavior with adb | deep-links | references/deep-links/README.md |
| I want to handle the back button and predictive back gestures with BackHandler / PredictiveBackHandler | back-navigation | references/back-navigation/README.md |
| I want to implement custom back handling with OnBackPressedDispatcher / OnBackInvokedDispatcher | back-navigation | references/back-navigation/README.md |
navigation3's ListDetailSceneStrategy / SupportingPaneSceneStrategy only handle the logic for placing the back stack into a Scene. UI components such as NavigationBar / TopAppBar should be android-compose-components, and the actual layout UI for list-detail and supporting pane is handled by android-compose-ui .