Desktop GUI Dev

Overview

Use this skill only for Tauri desktop applications.

• Treat the app as a Tauri shell with an unprivileged frontend, a Rust native layer, local data or persistence, and platform integration.
• Keep frontend contracts, Rust commands, capabilities, packaging metadata, and runtime behavior aligned across every surface you touch.
• Do not add guidance for other desktop frameworks to this skill.

Start Here

• Determine whether the user wants a new Tauri app, a feature addition, a bug fix, or packaging and release work.
• Read the actual build files and app manifests before editing. Prefer source over stale docs.
• If the user does not specify implementation choices and the repo does not already constrain them, default to Tauri 2.x, React 19 + TypeScript, Tailwind CSS 4, Zustand, SQLite via Rust rusqlite, and Recharts.
• Use rg for search and keep changes scoped to the smallest set of files that preserves frontend, Rust, capability, and packaging consistency.
• For scaffold commands, prerequisites, plugin setup, permissions, packaging, signing, updater work, and security-sensitive defaults, prefer the official Tauri docs when they differ from memory or repo notes.
• Read references/tauri.md for Tauri project creation, command boundaries, capabilities, plugins, packaging, and validation.