rn-router

Select, implement, and migrate React Native navigation solutions with version-specific guidance.

2|Updated May 20, 2026
One-click install
npx skills add https://github.com/Yemomo511/hybrid-agent-rail --skill rn-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rn-router
Source: https://github.com/Yemomo511/hybrid-agent-rail/tree/main/example/.codex/skills/rn-router
Command: npx skills add https://github.com/Yemomo511/hybrid-agent-rail --skill rn-router

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the guesswork and common errors involved in selecting, implementing, and migrating navigation solutions for React Native projects, reducing time spent resolving version incompatibilities, incorrect router choices, and broken deep linking or routing behavior.

Core Features & Use Cases

  • Navigation Selection Guidance: Uses a decision matrix to recommend Expo Router or React Navigation based on project type (Expo CLI, Community CLI, existing navigation setup) and requirements (Web support, deep linking, custom navigators).
  • Implementation References: Provides step-by-step guidance for setting up both Expo Router (file-based routing, layout primitives, Stack/Tabs/Drawer) and React Navigation (static/dynamic config, navigator types, linking setup) with version-specific syntax for Expo SDK 52-56 and React Navigation 5/6/7.
  • Migration & Best Practices: Includes workflows for migrating between the two navigation systems, plus scenario-specific best practices for common app types like auth flows, tab-based apps, admin panels, and custom navigators.

Quick Start

Use the rn-router skill to implement the correct navigation setup for my existing React Navigation 6 Expo app that needs to add deep linking and Web routing support.

Frequently Asked Questions about rn-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between Expo Router and React Navigation for my React Native app?

Choosing between Expo Router and React Navigation depends on your project type and requirements like Web support, deep linking, and custom navigators. A decision matrix evaluates your Expo CLI or Community CLI setup to recommend the correct navigation solution.

How do I set up deep linking and Web routing in an existing React Navigation app?

To set up deep linking and Web routing in React Navigation, you need to configure static or dynamic linking properties and ensure cross-platform routing compatibility. Version-specific guidance for React Navigation 5, 6, and 7 provides the exact syntax required.

Can I migrate my React Native navigation setup from React Navigation to Expo Router?

You can migrate from React Navigation to Expo Router using established migration workflows. The process involves transitioning to file-based routing and layout primitives while handling version compatibility for Expo SDK 52 through 56.

Does Expo Router support cross-platform routing for iOS, Android, and Web?

Expo Router supports cross-platform routing for iOS, Android, and Web. It utilizes file-based routing and layout primitives like Stack, Tabs, and Drawer to ensure consistent navigation behavior across all platforms.

What are the best practices for implementing auth flows in React Native navigation?

Best practices for implementing auth flows in React Native navigation involve using appropriate navigator types and conditional rendering based on authentication state. Guidance covers both Expo Router and React Navigation architectures for secure and scalable routing.

Are there version compatibility limitations when using React Navigation with Expo SDK 52?

React Navigation has specific version compatibility requirements with Expo SDK 52 through 56. Using mismatched React Navigation versions, specifically 5, 6, or 7, can cause routing errors and broken deep linking behavior if not configured correctly.