Tauri v2+ development: Rust backend, IPC, permissions, mobile builds
Build cross-platform desktop/mobile apps — tauri.conf.json, Rust commands, IPC patterns, capabilities/permissions, troubleshooting
- What
- Build cross-platform desktop/mobile apps — tauri.conf.json, Rust commands, IPC patterns, capabilities/permissions, troubleshooting
- Cost
- Free
- Needs
- the Tauri toolchain installed (@tauri-apps/cli, Rust, platform SDKs for mobile targets) and a Tauri project to work on — the skill is guidance the agent follows, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @nodnarbnitram's Tauri v2+ development skill: build cross-platform desktop and mobile apps with a web frontend and Rust backend. Quick start: create Tauri commands (#[tauri::command]) and register them in generate_handler! (unregistered commands silently fail), call them from the frontend with @tauri-apps/api/core (the v1 @tauri-apps/api/tauri API is gone), and declare capabilities/permissions — Tauri v2 denies everything by default. Critical rules: owned types (never &str) in async commands, never block the main thread, all shared logic in lib.rs (main.rs stays a thin passthrough — required for mobile), capabilities added before any plugin feature is used. Includes the tauri.conf.json configuration reference (devUrl, CSP, bundling), a known-issues prevention table (command not found, permission denied, white screen, mobile build failures, sidecar/updater issues), IPC patterns (events, channels, state management with Mutex<T>, error handling across the serde boundary), plugin list with mandatory permission strings, mobile-vs-desktop behavioral differences, and a setup checklist. Honest caveats: code-first reference — the agent still needs the Tauri toolchain installed (npx tauri info, Rust targets, platform SDKs for mobile) and a real project; verified against official docs as of 2026-04-02 — check the Tauri changelog for newer changes. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: the Tauri toolchain installed (@tauri-apps/cli, Rust, platform SDKs for mobile targets) and a Tauri project to work on — the skill is guidance the agent follows, not software to install Install "Tauri v2+ development: Rust backend, IPC, permissions, mobile builds" for me. It gives my agent @nodnarbnitram's Tauri v2+ reference: create and register Rust commands (generate_handler!), call them from the frontend, declare capabilities/permissions (deny-by-default), configure tauri.conf.json, use IPC events/channels and state patterns, handle errors across the serde boundary, and troubleshoot the 8+ common errors (missing capabilities, unregistered commands, white screen, mobile build failures) — plus deep-dive reference files for capabilities, IPC, plugins, updater/distribution and advanced runtime topics. MIT-licensed. Repository: https://github.com/nodnarbnitram/claude-code-extensions/blob/main/.claude/skills/tauri-v2/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "tauri-v2". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at my Tauri project; verify `npx tauri info` shows correct v2 versions). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.