AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
mobilecritical PriorityID: react-native-nitro-zero-copy-memory-bridge

React Native 0.76 Nitro Modules Zero-Copy Direct Memory Bridge Standard

Enforces zero-copy byte-level buffer sharing between native graphics/audio threads and Hermes JavaScript via Nitro Modules C++ ArrayBuffers. Prohibits base64 stringification, JSON serialization, and unmanaged raw pointer lifetime hazards that induce SIGSEGV or bridge stalls.

Prohibited Anti-Pattern: Serializing High-Frequency Binary Streams via Base64/JSON Strings and Dangling Raw Pointers Across Native-Hermes Boundaries

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: React Native 0.76 Nitro Modules Zero-Copy Direct Memory Bridge Standard - Enforces zero-copy byte-level buffer sharing between native graphics/audio threads and Hermes JavaScript via Nitro Modules C++ ArrayBuffers. Prohibits base64 stringification, JSON serialization, and unmanaged raw pointer lifetime hazards that induce SIGSEGV or bridge stalls.
globs: src/**/*.{ts,tsx}, nitro.json, cpp/**/*.{h,hpp,cpp}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/react-native-nitro-zero-copy-memory-bridge"
---

# React Native 0.76 Nitro Modules Zero-Copy Direct Memory Bridge Standard

> **Severity**: CRITICAL | **Category**: mobile
> **Anti-Pattern Warning**: Serializing High-Frequency Binary Streams via Base64/JSON Strings and Dangling Raw Pointers Across Native-Hermes Boundaries

## System Constraints
You are a Principal Engineer enforcing React Native 0.76 Nitro Modules C++ zero-copy memory bridging. Mandate strict invariants around direct memory exchange between native threads (graphics, audio, camera) and Hermes JSI ArrayBuffers without intermediate allocations or base64 serialization.

## Strict Guidelines
- Engineers MUST ALWAYS expose high-throughput native byte streams to Hermes using Nitro `ArrayBuffer` or `ArrayBufferHolder` backed by `std::shared_ptr<uint8_t[]>` with deterministic custom deleters.
- Engineers MUST NOT convert binary buffers to Base64 strings, numeric arrays (`number[]`), or JSON payloads across the native-JS boundary under any circumstances.
- Code SHOULD wrap mutable Hermes-allocated `ArrayBuffer` memory into `std::span<uint8_t>` on the C++ side to eliminate intermediate copy passes during synchronous reads.
- Services MUST synchronize multi-threaded access using lock-free single-producer single-consumer (SPSC) ring buffers or double-buffering mechanisms when native audio/render threads stream to Hermes.
- Components NEVER hold unmanaged raw pointers (`uint8_t*`) across asynchronous boundaries without explicit reference counting tying the memory lifetime to the JS garbage collector via Nitro's host object lifecycle.

## Bad vs Good Implementations
### Audio PCM Buffer Bridge (Nitro Modules C++ & TypeScript)

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Encodes PCM audio frames into Base64 strings and passes them through string allocation pipelines. This induces catastrophic JavaScript GC thrashing, copies memory multiple times across the bridge, and defeats Hermes engine direct memory access.
```typescript
// TypeScript Interface
export interface IAudioProcessor {
  // Anti-pattern: High-frequency audio frames converted to Base64 string
  processAudioFrame(base64Chunk: string): string;
}

// Native consumption creates huge GC pressure and serialization latency
export function handleMicInput(audioBytes: Uint8Array, processor: IAudioProcessor): Uint8Array {
  const base64 = btoa(String.fromCharCode(...audioBytes));
  const resultBase64 = processor.processAudioFrame(base64);
  return Uint8Array.from(atob(resultBase64), c => c.charCodeAt(0));
}
```

#### Production Standard (Correct)
> **Standard**: Passes the `ArrayBuffer` directly across the Nitro JSI bridge into C++, allowing the native audio DSP pipeline to inspect and mutate memory in-place via `std::span` without copying or serializing.
```typescript
// TypeScript Interface (Nitro spec)
import type { ArrayBuffer } from 'react-native-nitro-modules';

export interface IAudioProcessor {
  // Zero-copy direct memory handle passing
  processAudioFrame(buffer: ArrayBuffer): void;
}

// Zero-copy consumption: ArrayBuffer backed by shared native heap
export function handleMicInput(pcmBuffer: ArrayBuffer, processor: IAudioProcessor): void {
  // Directly pass the underlying buffer handle to Nitro C++ bridge
  // No allocations, no Base64 transforms, zero JS-thread GC pauses
  processor.processAudioFrame(pcmBuffer);
}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Nitro Modules AST & Binding Validator
Validates Nitro specification interfaces against C++ JSI bindings to guarantee zero-copy ArrayBuffer signatures.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Nitro Codegen CLI
Generates compile-time validated C++ JSI direct bindings from TypeScript specs for React Native 0.76+.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: React Native 0.76 Nitro Modules Zero-Copy Direct Memory Bridge Standard

React Native 0.76 Nitro Modules Zero-Copy Direct Memory Bridge Standard defines an industrial-grade behavioral standard for mobile engineering. Enforces zero-copy byte-level buffer sharing between native graphics/audio threads and Hermes JavaScript via Nitro Modules C++ ArrayBuffers. Prohibits base64 stringification, JSON serialization, and unmanaged raw pointer lifetime hazards that induce SIGSEGV or bridge stalls. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Serializing High-Frequency Binary Streams via Base64/JSON Strings and Dangling Raw Pointers Across Native-Hermes Boundaries Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftSerializing High-Frequency Binary Streams via Base64/JSON Strings and Dangling Raw Pointers Across Native-Hermes BoundariesCritical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST ALWAYS expose high-throughput native byte streams to Hermes using Nitro `ArrayBuffer` or `ArrayBufferHolder` backed by `std

Engineers MUST ALWAYS expose high-throughput native byte streams to Hermes using Nitro `ArrayBuffer` or `ArrayBufferHolder` backed by `std::shared_ptr<uint8_t[]>` with deterministic custom deleters.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT convert binary buffers to Base64 strings, numeric arrays (`number[]`), or JSON payloads across the native-JS boundary under any circumstances.

Engineers MUST NOT convert binary buffers to Base64 strings, numeric arrays (`number[]`), or JSON payloads across the native-JS boundary under any circumstances.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Code SHOULD wrap mutable Hermes-allocated `ArrayBuffer` memory into `std

Code SHOULD wrap mutable Hermes-allocated `ArrayBuffer` memory into `std::span<uint8_t>` on the C++ side to eliminate intermediate copy passes during synchronous reads.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Services MUST synchronize multi-threaded access using lock-free single-producer single-consumer (SPSC) ring buffers or double-buffering mechanisms when native audio/render threads stream to Hermes.

Services MUST synchronize multi-threaded access using lock-free single-producer single-consumer (SPSC) ring buffers or double-buffering mechanisms when native audio/render threads stream to Hermes.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Components NEVER hold unmanaged raw pointers (`uint8_t*`) across asynchronous boundaries without explicit reference counting tying the memory lifetime to the JS garbage collector via Nitro's host object lifecycle.

Components NEVER hold unmanaged raw pointers (`uint8_t*`) across asynchronous boundaries without explicit reference counting tying the memory lifetime to the JS garbage collector via Nitro's host object lifecycle.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is React Native 0.76 Nitro Modules Zero-Copy Direct Memory Bridge Standard critical for AI coding assistants?

Enforces zero-copy byte-level buffer sharing between native graphics/audio threads and Hermes JavaScript via Nitro Modules C++ ArrayBuffers. Prohibits base64 stringification, JSON serialization, and unmanaged raw pointer lifetime hazards that induce SIGSEGV or bridge stalls. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Serializing High-Frequency Binary Streams via Base64/JSON Strings and Dangling Raw Pointers Across Native-Hermes Boundaries) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related MOBILE Rules

View all rules →
mobile
106

Tauri 2.0 Mobile IPC & Capabilities Permissions Matrix Standard

Tauri v2 introduces a capability-driven permissions system replacing legacy v1 allowlists across iOS and Android runtimes. Failure to constrain IPC command handlers with typed schemas and explicit mobile capability definitions exposes native mobile OS surfaces to arbitrary code execution, permission leakage, and silent serialization failures. Production mobile deployments require strictly typed IPC boundary validation, granular capability scopes, and graceful permission degradation.

mobile
70

Capacitor 7 Native Bridge, Biometric Auth & Android 15 Lifecycle Production Standard

Capacitor 7 enforces strict bridge lifecycle contracts, asynchronous native plugin interop, and mandatory Android 15 edge-to-edge window inset handling. Storing sensitive authentication tokens in unencrypted web storage or failing to bind biometric authentication directly to hardware-backed Keystore or Secure Enclave mechanisms compromises app integrity and causes fatal crash or viewport occlusion issues on modern mobile operating systems.

mobile
58

Tauri 2.0 Mobile IPC Isolation and Capabilities Permission Scoping

Enforces strict capability permission boundaries, payload validation, and secure IPC invoke scoping for Tauri v2 Android and iOS environments. Prevents arbitrary IPC command execution, excessive native privilege granting, and deserialization vulnerabilities across the mobile webview-native boundary.

1 Rule in Stack

React