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: tauri-v2-mobile-ipc-zero-copy-arraybuffer-boundary

Tauri 2.0 Zero-Copy Binary IPC Buffer Boundary Enforcement

Enforces raw binary buffer transfers between the WebView JavaScript runtime and Rust backend in Tauri 2.0 mobile applications. Mandates the use of raw ArrayBuffer, Uint8Array, and Tauri IPC Channels or raw Responses, eliminating JSON serialization and deserialization overhead that causes main-thread frame drops and memory spikes during high-frequency telemetry or binary streaming.

Prohibited Anti-Pattern: Serializing High-Frequency Binary Streams into JSON Arrays or Base64 Strings Across Tauri IPC

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Tauri 2.0 Zero-Copy Binary IPC Buffer Boundary Enforcement - Enforces raw binary buffer transfers between the WebView JavaScript runtime and Rust backend in Tauri 2.0 mobile applications. Mandates the use of raw ArrayBuffer, Uint8Array, and Tauri IPC Channels or raw Responses, eliminating JSON serialization and deserialization overhead that causes main-thread frame drops and memory spikes during high-frequency telemetry or binary streaming.
globs: src/**/*.{ts,tsx}, src-tauri/src/**/*.rs
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tauri-v2-mobile-ipc-zero-copy-arraybuffer-boundary"
---

# Tauri 2.0 Zero-Copy Binary IPC Buffer Boundary Enforcement

> **Severity**: CRITICAL | **Category**: mobile
> **Anti-Pattern Warning**: Serializing High-Frequency Binary Streams into JSON Arrays or Base64 Strings Across Tauri IPC

## System Constraints
You are a Principal Systems Architect enforcing strict zero-copy binary transfer boundaries across Tauri 2.0 mobile (Android WebView / iOS WKWebView) and Rust core runtimes. You must prohibit any serialization of binary payloads, sensor telemetry, audio frames, or image data through standard serde/JSON converters. Mandate raw ArrayBuffer transfers, Tauri 2.0 raw Request/Response IPC handlers, and typed binary Channel streams.

## Strict Guidelines
- Engineers MUST ALWAYS pass high-frequency or binary payloads (>64KB or >30Hz) as raw Uint8Array or ArrayBuffer instances directly through Tauri 2.0 binary IPC or custom streaming protocols.
- Engineers MUST NOT convert binary arrays into numeric JSON arrays (`Array.from(uint8Array)`) or Base64 strings when invoking Tauri commands on mobile targets.
- Code SHOULD leverage Tauri 2.0's `tauri::ipc::Response::new(bytes)` to stream binary responses back to JavaScript without invoking `serde_json::to_value`.
- Services MUST process streaming telemetry through Tauri 2.0 `Channel<Vec<u8>>` or continuous binary IPC streams to prevent WebView main-thread micro-stalls.
- Components NEVER bridge continuous sensor data (e.g., IMU, WebRTC audio, camera frames) over standard JSON-encoded `invoke()` boundaries.

## Bad vs Good Implementations
### Binary Streaming over Tauri 2.0 IPC

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Converting an ArrayBuffer into a JavaScript Array creates intermediate objects for every byte, resulting in severe garbage collector pressure and JSON serialization stalls that block the 60/120fps UI thread on mobile devices.
```typescript
import { invoke } from '@tauri-apps/api/core';

// Anti-pattern: Serializing binary buffer to JSON array causing memory allocation storms
export async function sendTelemetryFrame(buffer: ArrayBuffer): Promise<void> {
  const rawArray = Array.from(new Uint8Array(buffer));
  await invoke('process_frame', { 
    frameData: rawArray 
  });
}
```

#### Production Standard (Correct)
> **Standard**: Directly passing typed binary buffers via Tauri 2.0 raw IPC envelopes transmits data directly through native platform bridges (WKWebView message handlers / Android evaluateJavascript/addJavascriptInterface) without JSON encoding overhead.
```typescript
import { invoke } from '@tauri-apps/api/core';

// Production standard: Passing raw Uint8Array using Tauri 2.0 binary IPC envelope
export async function sendTelemetryFrame(buffer: ArrayBuffer): Promise<Uint8Array> {
  const payload = new Uint8Array(buffer);
  const response = await invoke<ArrayBuffer>('process_frame_raw', payload, {
    headers: {
      'content-type': 'application/octet-stream'
    }
  });
  return new Uint8Array(response);
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Tauri Documentation MCP
Provides schema validation and API reference for Tauri 2.0 IPC interfaces and mobile platform bindings.
Recommended Agent Skills (askills.dev)

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

Cargo Mobile Check
Validates Rust compile targets and IPC handler signatures for Android NDK and iOS architectures.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tauri 2.0 Zero-Copy Binary IPC Buffer Boundary Enforcement

Tauri 2.0 Zero-Copy Binary IPC Buffer Boundary Enforcement defines an industrial-grade behavioral standard for mobile engineering. Enforces raw binary buffer transfers between the WebView JavaScript runtime and Rust backend in Tauri 2.0 mobile applications. Mandates the use of raw ArrayBuffer, Uint8Array, and Tauri IPC Channels or raw Responses, eliminating JSON serialization and deserialization overhead that causes main-thread frame drops and memory spikes during high-frequency telemetry or binary streaming. 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 into JSON Arrays or Base64 Strings Across Tauri IPC 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 into JSON Arrays or Base64 Strings Across Tauri IPCCritical
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 pass high-frequency or binary payloads (>64KB or >30Hz) as raw Uint8Array or ArrayBuffer instances directly through Tauri 2.0 binary IPC or custom streaming protocols.

Engineers MUST ALWAYS pass high-frequency or binary payloads (>64KB or >30Hz) as raw Uint8Array or ArrayBuffer instances directly through Tauri 2.0 binary IPC or custom streaming protocols.

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 arrays into numeric JSON arrays (`Array.from(uint8Array)`) or Base64 strings when invoking Tauri commands on mobile targets.

Engineers MUST NOT convert binary arrays into numeric JSON arrays (`Array.from(uint8Array)`) or Base64 strings when invoking Tauri commands on mobile targets.

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 leverage Tauri 2.0's `tauri

Code SHOULD leverage Tauri 2.0's `tauri::ipc::Response::new(bytes)` to stream binary responses back to JavaScript without invoking `serde_json::to_value`.

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 process streaming telemetry through Tauri 2.0 `Channel<Vec<u8>>` or continuous binary IPC streams to prevent WebView main-thread micro-stalls.

Services MUST process streaming telemetry through Tauri 2.0 `Channel<Vec<u8>>` or continuous binary IPC streams to prevent WebView main-thread micro-stalls.

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 bridge continuous sensor data (e.g., IMU, WebRTC audio, camera frames) over standard JSON-encoded `invoke()` boundaries.

Components NEVER bridge continuous sensor data (e.g., IMU, WebRTC audio, camera frames) over standard JSON-encoded `invoke()` boundaries.

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 Tauri 2.0 Zero-Copy Binary IPC Buffer Boundary Enforcement critical for AI coding assistants?

Enforces raw binary buffer transfers between the WebView JavaScript runtime and Rust backend in Tauri 2.0 mobile applications. Mandates the use of raw ArrayBuffer, Uint8Array, and Tauri IPC Channels or raw Responses, eliminating JSON serialization and deserialization overhead that causes main-thread frame drops and memory spikes during high-frequency telemetry or binary streaming. 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 into JSON Arrays or Base64 Strings Across Tauri IPC) 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

Tauri