What problem does it solve? Crossing language boundaries in Rust projects involves subtle ownership, panic, and toolchain concerns that cause crashes and undefined behavior when handled as mere binding syntax. This Skill structures interop work as a boundary discipline problem with curated reference material for each integration lane. ## Core Features & Use Cases - Lane-Based Guidance: Branches into dedicated references for C/C++ FFI, Python via PyO3 and Maturin, Node native addons, Rust-TypeScript/WASM bridges, and Tauri core-shell IPC. - Boundary Identification: Requires explicitly naming the panic boundary, ownership boundary, and toolchain boundary before implementation begins. - Use Case: When exposing a Rust crate to Python, follow the PyO3/Maturin lane to design safe ownership transfer across the FFI boundary instead of guessing at binding syntax. ## Quick Start Ask the assistant to help you build Python bindings for your Rust crate using PyO3 and Maturin with proper boundary handling.