tauri-stinger

Run the official tauri migrate command on a feature branch, then review the output in bounded slices: entry point, configuration keys, pluginified APIs, allowlist-to-capability conversion, events, and updater compatibility. The Skill's migration guide and example walk through each slice with verification steps.

Use a Tauri Channel attached to an authorized command with a tagged Serde enum for Started, Token, Completed, and Failed events. The Skill provides a derived typed-Channel example in Rust and TypeScript, plus cancellation and terminal-state rules.

Commands registered only through invoke_handler are available to all windows by default. Declare them via AppManifest::commands in build.rs, define named permissions, and bind them to capabilities scoped to specific windows, platforms, and origins.

Yes, on desktop via bundle.externalBin with one executable per target triple, spawned and owned by Rust. The Skill documents a bounded NDJSON protocol, raw-output reading, and lifecycle management; Android and iOS cannot spawn child processes.

The Cargo tauri crate and npm @tauri-apps/api package must share major and minor versions, and each plugin's Rust and npm halves must match exactly. Mismatches cause subtle IPC and behavior failures, so the inspector reports alignment before upgrades.

Use rust-stinger for general Rust design, a framework Stinger for frontend internals, security-stinger for formal audits, and ci-release-stinger for CI topology. This Skill covers only Tauri-specific integration, migration, and distribution work.