What problem does it solve? Setting up a Rust-based WASM frontend (Leptos, Yew, Dioxus, Sycamore) inside a Tauri v2 desktop or mobile app involves many interlocking configuration files, and small mistakes in Trunk.toml, tauri.conf.json, or Cargo.toml cause WASM loading failures, broken hot-reload, or undefined Tauri APIs. ## Core Features & Use Cases - Complete Configuration Templates: Provides working tauri.conf.json, Trunk.toml, Cargo.toml, and index.html setups with explanations of critical settings like withGlobalTauri, crate-type, and ws_protocol. - Framework-Specific Guidance: Includes Leptos component examples showing how to invoke Tauri backend commands via wasm-bindgen or the tauri-wasm crate. - Mobile Development Support: Covers the extra configuration needed for mobile hot-reload, including listening on 0.0.0.0 and using a local IP as devUrl. - Use Case: You are building a cross-platform desktop app with a Leptos frontend and need to call a Rust backend command from a button click; this Skill gives you the exact project structure, dependencies, and invoke pattern to make it work. ## Quick Start Set up a new Tauri v2 project with a Leptos WASM frontend, including Trunk configuration and a working greet command example.
