CtrlK
BlogDocsLog inGet started
Tessl Logo

android-legacy-navigation

Implement Jetpack Navigation Component with XML graphs and SafeArgs for type-safe fragment navigation. Use when working with XML-based Navigation Component or SafeArgs in Android. (triggers: navigation/*.xml, findNavController, NavDirections, navArgs)

83

Quality

78%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/android/android-legacy-navigation/SKILL.md
SKILL.md
Quality
Evals
Security

Android Legacy Navigation Standards

Priority: P1

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

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.

Claim skill