rn-newarch-modules-create

Create and migrate React Native native modules to TurboModule standards.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the guesswork and compatibility pitfalls of creating or migrating React Native native modules to the New Architecture TurboModule standard for RN 0.68-0.85 projects, ensuring correct implementation across different RN versions and platform requirements.

Core Features & Use Cases

  • Version-adaptive implementation: Automatically selects the correct TurboModule creation strategy based on the project's React Native version, handling opt-in new architecture for RN 0.68-0.73, default TurboModule requirements for RN 0.76+, and New Architecture-only rules for RN 0.82+.
  • Cross-platform module support: Guides implementation of Android/iOS native TurboModules or shared C++ cross-platform modules, including Codegen configuration, platform-specific registration, and build validation steps.
  • Legacy migration guardrails: Provides clear stop rules and pre-implementation checks to avoid incorrect migration of old bridge NativeModules, only proceeding when all required project context is confirmed. Use case: A developer working on an RN 0.78 e-commerce app can use this Skill to create a new TurboModule for native payment SDK integration, or migrate an existing old bridge module for user authentication to the new architecture without manual trial and error.

Quick Start

Ask the AI to create a new TurboModule for your React Native 0.80 app that exposes a native method to retrieve the device's current battery level, and it will guide you through TypeScript spec creation, Codegen setup, and Android/iOS native implementation with build validation.

Frequently Asked Questions about rn-newarch-modules-create

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

FAQPage Schema
How do I create a TurboModule for React Native New Architecture?

Creating a TurboModule for React Native New Architecture involves writing a TypeScript spec, configuring Codegen, and implementing Android/iOS native code. This process adapts based on your specific React Native version from 0.68 to 0.85.

Can I migrate a legacy NativeModule to the New Architecture TurboModule standard?

Yes, you can migrate legacy NativeModules to the New Architecture TurboModule standard. The migration includes pre-implementation checks and stop rules to ensure all required project context is confirmed before proceeding with the conversion.

Does React Native 0.76 require TurboModules for native development?

React Native 0.76+ defaults to TurboModule requirements for native development, and React Native 0.82+ enforces New Architecture-only rules. Projects between 0.68 and 0.73 require opting into the new architecture first.

How do I build a shared C++ cross-platform module in React Native?

Building a shared C++ cross-platform module in React Native requires configuring Codegen and implementing platform-specific registration for both Android and iOS. This ensures the shared native module functions correctly across both mobile platforms.

What is Codegen configuration used for in React Native TurboModules?

Codegen configuration in React Native TurboModules is used to automatically generate native interface code from your TypeScript specifications. This ensures type-safe communication between JavaScript and native Android/iOS implementations.

Why is my TurboModule not registering correctly on Android and iOS?

TurboModule registration failures on Android and iOS usually stem from missing platform-specific registration steps or incomplete Codegen configuration. Build validation is required to ensure the native module is correctly linked across both platforms.