cc-tauri-project-standard
Use when a Tauri application needs work on Rust commands, WebView IPC contracts, capabilities and permissions, managed state, desktop lifecycle, platform builds or release boundaries. A plain Rust lib
SKILL.mdskills/cc-tauri-project-standard/SKILL.md
GitHubTauri application engineering
Locate the owning web application and src-tauri crate. Treat UI and Rust core as application roles, regardless of the product supplying this skill.
- Read the actual Tauri/API/plugin versions, Cargo and JavaScript locks, configuration and supported platforms. Keep v1 and v2 permission models distinct; preserve the existing toolchain.
- Map each invoke to its Rust command, validated input, public result/error and resource owner. Keep filesystem/process authority in the core and expose narrow operations.
- Check command registration, app-command permission generation, capabilities, window/WebView labels and remote origins together. Permissions do not validate application-specific input.
- Define managed-state lifetimes, bounded blocking work, cancellation and shutdown. Review locks held across suspension and event listener cleanup.
- Use the practice checklist and minimal application. They include the local command contract needed without another skill package.
- Follow verification boundaries: test rejected input before effects, then verify actual WebView/permission activation, target bundles and signing in their own environments.
Deliver the affected UI/core roots, invoke contract, authority decisions, actual commands/results and unverified platforms. Source or unit checks alone do not establish a working desktop release.
Engineering practices
Read the local engineering decisions for this task and follow their links to relevant shared principles. Apply levels and exceptions against actual project contracts; product frontend/backend labels do not constrain language or role.