navigation-native-navigators — Claude Code rule: what it does
navigation-native-navigators is a Claude Code rule that steers React Native navigation toward native components. It covers stacks, tabs, and screen headers.
MIT ★ 1,216 updated 2026-10-24
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install react-skills@claude-settingsWhat navigation-native-navigators does
The rule favors native navigators over JavaScript-based navigation. For stacks, it points to @react-navigation/native-stack or the default expo-router stack. For tabs, it names react-native-bottom-tabs and expo-router native tabs.
It also recommends built-in header options instead of a custom header component. On iOS, native tabs adjust the root ScrollView insets automatically; disableAutomaticContentInsets turns that behavior off.
What it helps with
- replace a JavaScript stack with a native stack
- choose a native implementation for tab navigation
- configure a screen header with built-in options
Example prompts for the agent
- Use a native stack for navigation in my React Native app.
- Switch the
expo-routertabs to native tabs. - Show the screen title using native header options, not a custom component.
How to install navigation-native-navigators
1Plugin marketplace
/plugin marketplace add fcakyon/claude-codex-settings/plugin install react-skills@claude-settings2Manually: put the files in place
.claude/rules/navigation-native-navigators.mdThe paths frontmatter field limits the files
AGENTS.md
Codex reads AGENTS.md: paste the rule text there
Manually: put the files in place
.cursor/rules/navigation-native-navigators.mdcFrontmatter: description, globs, alwaysApply
Manually: put the files in place
.github/instructions/navigation-native-navigators.instructions.mdThe applyTo field sets which files it applies to
Manually: put the files in place
.devin/rules/navigation-native-navigators.mdManually: put the files in place
.clinerules/navigation-native-navigators.mdStep by step, with commands for each platform: AGENTS.md vs CLAUDE.md: what they are and which one to use
Questions about navigation-native-navigators
How do I install navigation-native-navigators in Claude Code?
Run /plugin marketplace add fcakyon/claude-codex-settings, then /plugin install react-skills@claude-settings. The rule file path is .claude/rules/navigation-native-navigators.md.
What does navigation-native-navigators do?
It directs React Native projects toward native stacks and tabs, and recommends built-in header options over custom header components.
Which navigators does the rule recommend?
For stacks, it names @react-navigation/native-stack or the default expo-router stack. For tabs, it recommends react-native-bottom-tabs or expo-router native tabs.
Source text
navigation-native-navigators.md · MIT
---
title: Use Native Navigators for Navigation
impact: HIGH
impactDescription: native performance, platform-appropriate UI
tags: navigation, react-navigation, expo-router, native-stack, tabs
---
## Use Native Navigators for Navigation
Always use native navigators instead of JS-based ones. Native navigators use
platform APIs (UINavigationController on iOS, Fragment on Android) for better
performance and native behavior.
**For stacks:** Use `@react-navigation/native-stack` or expo-router's default
stack (which uses native-stack). Avoid `@react-navigation/stack`.
**For tabs:** Use `react-native-bottom-tabs` (native) or expo-router's native
tabs. Avoid `@react-navigation/bottom-tabs` when native feel matters.
### Stack Navigation
**Incorrect (JS stack navigator):**
```tsx
import { createStackNavigator } from '@react-navigation/stack'
const Stack = createStackNavigator()
function App() {
return (
<Stack.Navigator>
<Stack.Screen name='Home' component={HomeScreen} />
<Stack.Screen name='Details' component={DetailsScreen} />
</Stack.Navigator>
)
}
```
**Correct (native stack with react-navigation):**
```tsx
import { createNativeStackNavigator } from '@react-navigation/native-stack'
const Stack = createNativeStackNavigator()
function App() {
return (
<Stack.Navigator>
<Stack.Screen name='Home' component={HomeScreen} />
<Stack.Screen name='Details' component={DetailsScreen} />
</Stack.Navigator>
)
}
```
**Correct (expo-router uses native stack by default):**
```tsx
// app/_layout.tsx
import { Stack } from 'expo-router'
export default function Layout() {
return <Stack />
}
```
### Tab Navigation
**Incorrect (JS bottom tabs):**
```tsx
import { createBottomTabNavigator } from '@react-navigation/bottom-tabs'
const Tab = createBottomTabNavigator()
function App() {
return (
<Tab.Navigator>
<Tab.Screen name='Home' component={HomeScreen} />
<Tab.Screen name='Settings' component={SettingsScreen} />
</Tab.Navigator>
)
}
```
**Correct (native bottom tabs with react-navigation):**
```tsx
import { createNativeBottomTabNavigator } from '@bottom-tabs/react-navigation'
const Tab = createNativeBottomTabNavigator()
function App() {
return (
<Tab.Navigator>
<Tab.Screen
name='Home'
component={HomeScreen}
options={{
tabBarIcon: () => ({ sfSymbol: 'house' }),
}}
/>
<Tab.Screen
name='Settings'
component={SettingsScreen}
options={{
tabBarIcon: () => ({ sfSymbol: 'gear' }),
}}
/>
</Tab.Navigator>
)
}
```
**Correct (expo-router native tabs):**
```tsx
// app/(tabs)/_layout.tsx
import { NativeTabs } from 'expo-router/unstable-native-tabs'
export default function TabLayout() {
return (
<NativeTabs>
<NativeTabs.Trigger name='index'>
<NativeTabs.Trigger.Label>Home</NativeTabs.Trigger.Label>
<NativeTabs.Trigger.Icon sf='house.fill' md='home' />
</NativeTabs.Trigger>
<NativeTabs.Trigger name='settings'>
<NativeTabs.Trigger.Label>Settings</NativeTabs.Trigger.Label>
<NativeTabs.Trigger.Icon sf='gear' md='settings' />
</NativeTabs.Trigger>
</NativeTabs>
)
}
```
On iOS, native tabs automatically enable `contentInsetAdjustmentBehavior` on the
first `ScrollView` at the root of each tab screen, so content scrolls correctly
behind the translucent tab bar. If you need to disable this, use
`disableAutomaticContentInsets` on the trigger.
### Prefer Native Header Options Over Custom Components
**Incorrect (custom header component):**
```tsx
<Stack.Screen
name='Profile'
component={ProfileScreen}
options={{
header: () => <CustomHeader title='Profile' />,
}}
/>
```
**Correct (native header options):**
```tsx
<Stack.Screen
name='Profile'
component={ProfileScreen}
options={{
title: 'Profile',
headerLargeTitleEnabled: true,
headerSearchBarOptions: {
placeholder: 'Search',
},
}}
/>
```
Native headers support iOS large titles, search bars, blur effects, and proper
safe area handling automatically.
### Why Native Navigators
- **Performance**: Native transitions and gestures run on the UI thread
- **Platform behavior**: Automatic iOS large titles, Android material design
- **System integration**: Scroll-to-top on tab tap, PiP avoidance, proper safe
areas
- **Accessibility**: Platform accessibility features work automatically
Reference:
- [React Navigation Native Stack](https://reactnavigation.org/docs/native-stack-navigator)
- [React Native Bottom Tabs with React Navigation](https://oss.callstack.com/react-native-bottom-tabs/docs/guides/usage-with-react-navigation)
- [React Native Bottom Tabs with Expo Router](https://oss.callstack.com/react-native-bottom-tabs/docs/guides/usage-with-expo-router)
- [Expo Router Native Tabs](https://docs.expo.dev/router/advanced/native-tabs)
© fcakyon · MIT · fcakyon/claude-codex-settings