Guide Rust engine development across WASM, desktop, CLI, and cloud targets.
npx skills add https://github.com/Develonaut/bnto --skill rust-expert-develonaut
Please help me install this Agent Skill. Skill: rust-expert Source: https://github.com/Develonaut/bnto/tree/main/.claude/skills/rust-expert Command: npx skills add https://github.com/Develonaut/bnto --skill rust-expert-develonaut
Guides teams in designing, reviewing, and implementing a portable, high-performance Rust engine that powers multiple targets (browser WASM, desktop, CLI, and cloud) from a unified codebase.
Employ this Rust engine expert persona to audit and improve the Rust codebase and its documentation.
High-intent search queries and answers about installing and using this skill.
Designing a Rust engine for WASM and native targets requires target-agnostic node architecture across core engine crates, isolating platform-specific bindings to ensure portable execution across browser, desktop, CLI, and cloud environments.
Handling ownership in a multi-crate Rust workspace involves defining explicit borrowing patterns across crate boundaries, ensuring safe memory management and robust error handling while maintaining clean code separation throughout the engine.
TDD-first testing is required for Rust code before adding WASM bindings to ensure robust error handling and safety. Thoroughly test core engine crates before compiling to WASM to prevent runtime failures in browser environments.
WASM runtime error handling fails across targets when error types are not designed target-agnostically. Implement robust error handling with explicit wasm-specific patterns and ownership guidance to ensure consistent behavior across browser and native environments.
A single Rust codebase can power CLI, desktop, and cloud engines by applying target-agnostic node design across unified core crates, exposing platform-specific functionality through separate binding crates for each execution target.
Compiling a Rust engine to WASM introduces limitations around ownership patterns, wasm-specific error handling, and target-agnostic node design constraints, requiring explicit architectural guidance to maintain safety and portability across browser and native targets.
OpenZeppelinSet up Soroban/Stellar smart contract projects with OpenZeppelin Rust crate dependencies.
kazukitcyReview and refactor public Rust API surfaces against Rust and Microsoft guidelines.
gregoryraymondDesign Rust crate ecosystems, Cargo workspaces, and FFI strategies.
ortus-boxlangCompile and execute BoxLang bytecode on the native Rust runtime without the JVM.
