rnn-codebase

Trace Navigation.push() command flows across JS/TS, iOS, and Android layers.

13.2k|2.6k|Updated Mar 11, 2016
One-click install
npx skills add https://github.com/wix/react-native-navigation --skill rnn-codebase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rnn-codebase
Source: https://github.com/wix/react-native-navigation/tree/main/.cursor/skills/rnn-codebase
Command: npx skills add https://github.com/wix/react-native-navigation --skill rnn-codebase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Navigate and understand the react-native-navigation (RNN) codebase to diagnose bugs, add features, and trace command flows across JS/TS, iOS, and Android layers.

Core Features & Use Cases

  • Cross-layer architecture mapping and command flow tracing across JS and native layers
  • Guidance for debugging, feature integration, and architecture comprehension
  • Use Case: When you need to understand how push/present flows traverse components, TurboModules, and platform-specific controllers

Quick Start

Read the RNN codebase structure and ARCHITECTURE.md to begin tracing a feature end-to-end.

Frequently Asked Questions about rnn-codebase

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

FAQPage Schema
How do I trace a react-native-navigation command flow across JS and native layers?

Trace react-native-navigation command flows by following calls from JS through Commands.ts to NativeCommandsSender.ts and into iOS/Android controllers, using the codebase structure and ARCHITECTURE.md as a map for cross-layer navigation.

How does Navigation.push resolve options in the react-native-navigation codebase?

Navigation.push resolves options by traversing JS/TS logic into native iOS and Android controllers, passing through TurboModules and platform-specific option resolution mechanisms detailed in the RNN architecture documentation.

Can I use this to debug react-native-navigation bugs across iOS and Android?

Yes, you can debug react-native-navigation bugs across iOS and Android by mapping the cross-layer architecture and tracing how push and present flows traverse components, TurboModules, and platform-specific controllers to diagnose issues.

Do I need to read ARCHITECTURE.md before navigating the RNN codebase?

Yes, reading ARCHITECTURE.md is required to understand the RNN architecture and repository structure before tracing features end-to-end across JS/TS, iOS, and Android layers effectively.

What's the best way to understand cross-language interactions in react-native-navigation?

The best way to understand cross-language interactions is tracing command flows from JS through Commands.ts and NativeCommandsSender.ts into native iOS and Android controllers, using architecture documentation to map the interactions.

Why does my react-native-navigation push command not reach the native iOS controller?

A push command may not reach the native iOS controller due to breaks in the cross-layer flow between JS, Commands.ts, and NativeCommandsSender.ts, which you can diagnose by tracing the command flow and checking architecture mappings.