What problem does it solve? Building Tauri v2 applications involves a mandatory capabilities-based security model, strict command registration rules, and platform-specific build requirements that cause silent runtime failures, permission errors, and broken mobile builds when misconfigured. ## Core Features & Use Cases - Rust Command & IPC Patterns: Implement #[tauri::command] functions with proper error handling, and choose between Commands, Events, and typed Channels for frontend-backend communication. - Security Capabilities Configuration: Set up capability files with explicit permissions and scopes for core APIs and official plugins (fs, dialog, shell, http, store, updater, and more). - Cross-Platform Build & Distribution: Configure tauri.conf.json and Cargo.toml for desktop (macOS, Windows, Linux) and mobile (iOS, Android), including updater signing and bundle packaging. - Use Case: When your invoke() call returns undefined or a plugin silently fails, this Skill diagnoses the missing generate_handler! registration or absent capability permission and provides the exact fix. ## Quick Start Ask the AI to create a new Tauri v2 command with its frontend invoke call and the required capability permissions for your app.
