What does this skill do, and when should you use it?
This skill provides Android developers with a comprehensive guide and code examples for Jetpack Navigation 3. It includes a step-by-step migration guide from Navigation 2 to Navigation 3, documentation for type-safe navigation, and a rich set of recipes covering everything from basic API usage to advanced patterns like deep links, multiple back stacks, dialog/bottom sheet scenes, adaptive two-pane layouts, conditional navigation, returning results, modular navigation, and ViewModel integration. All content is tailored for modern Android apps using Jetpack Compose and Kotlin. Maintained by Google LLC, licensed under Apache-2.0.
Provides navigation-related tutorials, developer documentation, and code examples through links to Markdown files referenced in SKILL.md. Specifically, it guides users through migrating from Navigation 2 to Navigation 3, demonstrates basic API usage, using a saveable back stack, defining entries via DSL, building a bottom navigation bar with multiple back stacks, parsing and handling deep links, creating custom scenes (dialog, bottom sheet, list-detail, two-pane), applying Material Adaptive layouts, customizing animations, handling conditional navigation (e.g., authentication), modularizing navigation code with Hilt/Koin, passing arguments to ViewModels, and returning results as events or state.
- Android developers using Navigation 2 who need a migration guide to upgrade to Navigation 3
- Developers who want to implement a bottom navigation bar with independent back stack history for each tab in Compose
- Developers who need to handle deep links from external Intents and ensure correct back stack behavior
- Developers who want to implement adaptive list-detail or two-pane layouts for different screen sizes (phone/tablet)
- Developers who wish to modularize navigation code using Hilt or Koin for large-scale projects
- Developers who need to return results to a previous destination, either as events or state
How do you install this skill?
- Relies on overseas services (e.g., developer.android.com) which may be inaccessible from mainland China; use proxy or mirror.
- Migration guide assumes project meets specific conditions; user must confirm before use to avoid incomplete migration.
- Static review cannot verify code runnability; validate in actual project.
This skill is part of the android/skills repository, which bundles multiple skills. To install this specific skill, you can use the Android CLI tool: run android skills add --skill=navigation-3 --project=. from your project root. Alternatively, manually place the SKILL.md file and its referenced references directory into your agent's skills folder (e.g., ~/.gemini/antigravity/skills/navigation-3/).
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/android/skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/navigation/navigation-3" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- Use the navigation-3 skill to provide steps for migrating from Navigation 2 to Navigation 3.
- Refer to the navigation-3 skill's recipes to implement a bottom navigation bar with multiple back stacks.
After installation, you can reference the skill in your prompts, for example: "Use the navigation-3 skill to provide steps for migrating from Navigation 2 to Navigation 3." or "Refer to the navigation-3 skill's recipes to implement a bottom navigation bar with multiple back stacks." The skill will guide you to the relevant Markdown guides and code examples.
What are this skill's strengths and limitations?
- Provided and maintained by Google, ensuring authoritative content aligned with official documentation
- Covers a wide range of scenarios from basic to advanced, including migration, deep links, adaptive layouts, and architecture patterns
- Offers code examples that can be directly used in practice
- Actively updated, last updated in 2026
- Follows the open Agent Skills standard, making it easy to integrate
- Content consists only of links to Markdown files, not actual code snippets within the skill itself; users need to manually access and copy examples
- No test or verification steps included; users must validate examples themselves
- Primarily focused on Compose and Kotlin, with limited support for legacy View systems (only mentions interop)
- Installation requires the Android CLI tool, which may add learning overhead for those unfamiliar with it
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Jetpack Navigation 3 Guide and Recipes this page | 59 · Recommended | ★ 7.7k | 16d ago | Apache-2.0 |
| Android Adaptive UI Skill | 71 · Strongly recommended | ★ 7.7k | 16d ago | Apache-2.0 |
| Jetpack Compose Styles Integration Skill | 44 · Not recommended | ★ 7.7k | 16d ago | Apache-2.0 |
| CameraX Development Skill | 60 · Recommended | ★ 7.7k | 16d ago | Apache-2.0 |
| Expo Native UI Builder | 59 · Recommended | ★ 2.7k | 6d ago | MIT |
This skill is the official Android skill for Jetpack Navigation 3, distinct from Navigation 2, and includes a migration guide. It does not compare directly with third-party navigation libraries like Voyager or Decompose.
How did FollowSkills review this skill?
The skill provides only operational guidance for navigation implementation, with no high-risk permission operations, dependencies are declared in official docs, no hidden data flow or sensitive data handling. However, missing explicit user confirmation or rollback steps, and unverified provenance, deductions applied.
Core migration steps and code examples are self-consistent, but rely on external libraries and APIs, static review cannot verify runnability, error handling only prompts user to check assumptions, lacks detailed failure feedback.
Target scenario clear: developers using Compose and migrating from Navigation 2 to Navigation 3. But boundary conditions require user self-check, and no consideration for mainland China network reachability, relies on overseas services, deductions applied.
Documentation structure clear with migration guide, recipes, references, but lacks version history and changelog, maintenance responsibility only implied by author, no explicit update path.
Core migration steps and code examples should guide completion, but static review cannot verify direct usability, user must validate.
Recipes reference official GitHub repos and developer docs, but lack independent verification evidence, static review cannot confirm authenticity.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →