Navigation
Use this skill for moving between screens.
When to use
- Adding or changing a screen or navigator registration
- Navigating from a component
- Navigating from a saga, Engine, or other non-UI caller
- Writing tests that assert navigation
- Reviewing a PR that introduces or changes navigation
Workflow
- Pick the route name from the shared route map. Do not invent a string.
- From a screen, navigate with the navigation hook. From a non-UI caller, use the navigation service.
- Pass typed params. Register the screen on an existing navigator tree.
- In tests, mock the navigation hook or the navigation service the same way nearby tests already do.