Navigation Usage

How to respond

If the user invoked this skill without a concrete task, start with a short explanation of what this plugin does and when it should be used.
Show how to use it through concrete navigation tasks this plugin can handle.
Point to the router-selection rule first, then the matching router-specific rule. Route to related plugins only when the task expands into DI or broader architecture decisions.
If the user already gave a concrete navigation task, briefly explain why this plugin fits and then do the work.
Before applying router-specific conventions, inspect pubspec.yaml and existing route files to decide whether the project uses auto_route or go_router. If both are present during a migration, follow the convention already used by the edited route tree unless the user asks to migrate it.
Do not reply with filler like "skill loaded", "ready for the task", or "what would you like to do?" before explaining the plugin.

Covers LeanCode navigation conventions for both auto_route and go_router projects.
Guides route naming, paths, parameters, data passing, typed route APIs, and deep-link boundaries.
Covers auto_route concepts such as @RoutePage, AppRouter, generated route classes, guards, and AutoTabsRouter.
Covers go_router concepts such as AppGoRoute, route_tree.dart, package-level *_routes.dart, and typed shell routes.