What problem does it solve? Building communication between a Tauri frontend and Rust backend often results in untyped invoke calls, inconsistent error handling, and mismatched request/response contracts that break at runtime. ## Core Features & Use Cases - Typed IPC Contracts: Define Rust commands and register them in the Tauri builder with typed request/response payloads. - Type Generation Guidance: Apply tauri-specta or official generators to eliminate any-typed IPC between frontend and backend. - Error Handling Patterns: Establish validation and error response contracts for command failures. - Use Case: When adding a serial port read command to a Tauri 2.x app, use this Skill to define the Rust command, generate TypeScript bindings, and call it from Svelte with full type safety. ## Quick Start Ask the assistant to create a type-safe Tauri command with typed invoke bindings for your frontend feature.