What problem does it solve?
Tauri-specific development is hard to get right because you must coordinate Rust backend commands, a web frontend, safe IPC patterns, and Tauri’s capability-based security without introducing fragile or insecure architecture.
Core Features & Use Cases
- Tauri 2 routing and guidance: Decide when Tauri is the right choice versus Electron or Flutter, based on size, runtime needs, performance, security posture, and plugin ecosystem.
- IPC and command system patterns: Implement reliable request/response and event-driven communication between the web UI and Rust backend, including state and multi-window flows.
- Security-first configuration: Configure least-privilege capability scopes and CSP guidance to reduce attack surface, avoid risky defaults, and keep updates and permissions auditable.
- Project scaffolding and implementation review: Use the documented structure, command registration, typed frontend invoke wrappers, and verification checklist to improve correctness and maintainability for daily engineering work.
Quick Start
Use the tauri skill to help me design a secure IPC architecture for my Tauri 2 app by mapping my existing Rust #[tauri::command] functions and tauri.conf.json security settings to an appropriate frontend invoke/listen strategy.