What problem does it solve? Tauri v2 enforces a strict permission system where frontend code cannot access backend commands without explicit grants, and misconfigured capabilities cause confusing "not allowed" errors. This Skill guides you through defining permissions, scopes, and capabilities correctly so your app stays secure without breaking functionality. ## Core Features & Use Cases - Capability Configuration: Create JSON or TOML capability files that link permissions to specific windows, platforms, and remote URLs. - Scoped Allow/Deny Rules: Restrict filesystem, HTTP, and shell access using scope variables like $APPDATA and glob patterns, with deny rules taking precedence. - Custom & Plugin Permissions: Define custom permission sets in TOML, use auto-generated command permissions, and apply plugin defaults like fs:default or shell:allow-execute. - Use Case: You need your Tauri app to read and write files only inside its own data directory while blocking access to sensitive paths like ~/.ssh. This Skill shows you the exact capability JSON with scoped allow and deny entries. ## Quick Start Ask the assistant to configure Tauri permissions so the main window can read and write text files only within the app's data directory.
