← Search

Tauri v2+ development: Rust backend, IPC, permissions, mobile builds
Developer tools 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 35e7f7d
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: the Tauri toolchain installed (@tauri-apps/cli…

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

At a glance
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.

Version:

Quick answer

Tauri v2+ development: Rust backend, IPC, permissions, mobile builds is a free Muse skill that helps your Muse build cross-platform desktop and mobile apps with a web frontend and Rust backend, covering tauri.conf.json, Rust commands, IPC patterns, capabilities and permissions, mobile builds, and troubleshooting for common failures.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 35e7f7d

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/nodnarbnitram/claude-code-extensions/35e7f7deae689e12b94f9c242b8f59efe0f66476/.claude/skills/tauri-v2/SKILL.md Pinned version: install the code at commit 35e7f7deae689e12b94f9c242b8f59efe0f66476 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 35e7f7d · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
35e7f7d · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.