Rust Tauri Apps

Build Tauri v2 applications with small Rust command surfaces, secure capabilities, explicit IPC contracts, and maintainable distribution workflows.

Operating Model

Inspect the Tauri version and generated structure first: src-tauri, tauri.conf.json, capabilities, permissions, plugins, frontend invocation code, and CI/release scripts.
Treat every command as a public bridge contract. Validate input, return typed serializable results, and keep filesystem/shell/network capabilities narrow.
Prefer app-owned Rust services behind commands. Do not put large domain logic directly in #[tauri::command] functions.
Keep the capability model least-privilege by default. Avoid broad filesystem, shell, opener, and dialog permissions unless the user workflow truly needs them.
Coordinate with the general tauri-v2 skill when available for framework-specific current docs; use this skill for Rust architecture, security, testing, and command design.

references/tauri-v2-rust-backend.md for command/state/plugin architecture and typed IPC.
references/capabilities-security.md for permissions, filesystem/shell risk, secrets, updater, and secure defaults.
references/distribution-mobile.md for bundling, updater, sidecars, signing, desktop/mobile packaging, and release checks.