android-legacy-navigation
Implement Jetpack Navigation Component with XML graphs and SafeArgs for type-safe fragment navigation. Use when working with XML-based navigation or SafeArgs in legacy Android projects; defer drawer and other UI-chrome work to UI skills.
78
Quality
100%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Passed
No findings from the security scan
Android Legacy Navigation Standards
Priority: P1 (HIGH)
1. Set Up Single-Activity Architecture
- Use one Host Activity with
NavHostFragment. - Enable SafeArgs plugin — MANDATORY for passing data between fragments.
See XML graph & SafeArgs examples for NavHostFragment setup.
2. Manage Navigation Graphs
- Nested Graphs: Modularize
navigation/resources (e.g.,nav_auth.xml,nav_main.xml) to keep graphs readable. - Deep Links: Define explicit
<deepLink>in graph, not AndroidManifest intent filters.
3. Navigate with SafeArgs
See XML graph & SafeArgs examples for type-safe navigation usage.
Anti-Patterns
- No Raw String Bundle Keys: Use SafeArgs generated type-safe classes.
- No Manual Fragment commit(): Use NavController for all navigation.
References
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
9f695e8
- Last updated
- First committed
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.