tauri

Guide Tauri v2 command registration, IPC modeling, permissions, and debugging.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/Firzus/agent-skills --skill tauri-firzus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tauri
Source: https://github.com/Firzus/agent-skills/tree/main/skills/web/tauri
Command: npx skills add https://github.com/Firzus/agent-skills --skill tauri-firzus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you work safely and efficiently on Tauri v2 desktop and mobile apps by organizing the right checks, permissions, and Rust/frontend conventions for common app changes and debugging.

Core Features & Use Cases

  • Command and IPC work: Add or modify Rust commands, owned IPC types, and frontend invoke calls with matching names and casing.
  • Plugin and permission setup: Register plugins, assign the narrowest matching capability permissions, and diagnose permission-denied failures.
  • Desktop debugging and validation: Investigate app startup, dev server state, DevTools, CDP attach on Windows, and fallback instrumentation.
  • Use Case: You are adding a new Rust command to a Tauri app and need to update the handler, verify serialization, confirm permissions, and run the right checks without breaking the shell.

Quick Start

Use the tauri skill to inspect this app’s Tauri configuration, identify the relevant command or plugin change, and tell me the exact edits and validation steps I should apply.

Frequently Asked Questions about tauri

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new Rust command and update IPC calls in a Tauri v2 app?

To add a Tauri v2 command, register the Rust handler with matching frontend invoke names, ensure IPC types are owned, verify serialization, and apply layered validation across frontend, Rust, and shell checks.

Why does my Tauri plugin return a permission denied error on desktop?

Tauri plugin permission denied errors occur when capability scopes are too broad or missing. Assign the narrowest matching capability permissions to the plugin and confirm the access scope in the capabilities configuration.

What is the best way to debug Tauri app startup and invoke failures?

Debug Tauri app startup and invoke failures using evidence-first troubleshooting: inspect dev server state, attach DevTools via CDP on Windows, and apply fallback instrumentation to isolate shell and runtime errors.

Do I need owned IPC types when modeling data between Rust and frontend in Tauri v2?

Yes, Tauri v2 requires owned IPC types for command serialization. You must model data with owned structures to ensure safe data transfer across the Rust and frontend boundary without breaking runtime checks.

Can I use this Tauri workflow for both desktop and mobile app development?

Yes, this Tauri v2 workflow supports both desktop and mobile app development by guiding command registration, plugin permissions, window handling, and runtime debugging across both platforms.

How does capability-scoped plugin access work in Tauri v2?

Capability-scoped plugin access in Tauri v2 restricts plugin features to specific windows and webviews. You register the plugin and then map the narrowest permission set to a capability file to enforce security boundaries.