taurilisted

# Tauri Use this skill for Tauri v2+ apps with a web frontend and Rust backend. Prefer the project's existing conventions, then steer with four leading words: **owned IPC**, **capabilities-first**, **evidence ladder**, and **layered checks**. ## First Checks 1. Inspect `src-tauri/tauri.conf.json`, `src-tauri/Cargo.toml`, `src-tauri/src/lib.rs`, `src-tauri/src/main.rs`, and `src-tauri/capabilities/*.json`. 2. Identify the project's existing command runner and dev/build commands from lockfiles, `package.json`, scripts, and `build.beforeDevCommand`. 3. Note whether the app targets desktop only or mobile too. Mobile-compatible apps need the `lib.rs` entry point shape and platform guards. 4. If debugging a running app, read [debugging.md](debugging.md) before launching anything. Done when: every path in step 1 is accounted for, launch/test commands are identified (or stated absent from the project), and desktop-vs-mobile scope is stated. ## Choose The Workflow Pick one branch. Complete its criterion before claiming the task done. ### Adding a Rust command Apply **owned IPC**: owned serializable command inputs/outputs, register the command in `generate_handler![...]` or the project's invoke wrapper, match frontend invoke names and argument casing. Before editing `#[tauri::command]` handlers or frontend `invoke` calls, read [best-practices.md](best-practices.md) and apply its async, error, and state rules. Done when: every new or changed command is registere