tauri-app-plugin-permissions

When to use this skill

ALWAYS use this skill when the user mentions:

• Writing or auditing plugin permissions
• Plugin capability templates
• Cross-platform permission differences

Trigger phrases include:

• "plugin permissions", "capability template", "permissions schema"
• "plugin permissions", "permission templates", "platform differences"

How to use this skill

1. Enumerate feature → plugin permission needs
2. Separate plugin-defined permissions from app-enabled capabilities
3. Generate capabilities/default.json with minimal scope
4. Validate Windows/platform differences and adjust

Outputs

• Permission template per plugin
• Capability file with minimal scope
• Cross-platform audit checklist

Scope

• Boundary: Plugin permissions and capability configuration only
• Key points: Windows and platform capability differences
• Out of scope: plugin implementation details

References

• https://v2.tauri.app/llms.txt
• https://v2.tauri.app/learn/using-plugin-permissions/
• https://v2.tauri.app/zh-cn/learn/security/using-plugin-permissions/
• https://v2.tauri.app/learn/security/capabilities-for-windows-and-platforms/
• https://v2.tauri.app/zh-cn/learn/security/capabilities-for-windows-and-platforms/
• https://v2.tauri.app/learn/security/writing-plugin-permissions/
• https://v2.tauri.app/zh-cn/learn/security/writing-plugin-permissions/

Keywords

tauri permissions, plugin permissions, capabilities, scope, security, plugin permissions, permission templates, platform differences

Common Gotchas (Gotchas)

1. Version compatibility: Pay attention to the compatibility of the framework version and dependency libraries; APIs may differ across versions
2. Configuration file format: Configuration file format errors are the most common problem; it is recommended to use the editor's syntax checking
3. Environment variables: Ensure that all necessary environment variables are set correctly, and do not hard-code sensitive information
4. Dependency conflicts: When multiple versions coexist, pay attention to dependency conflicts and use a lock file to pin versions
5. Performance pitfalls: Pay attention to performance optimization in large-data scenarios, and avoid common problems such as N+1 queries

Usage flow

Step 1: Environment preparation

Ensure that the necessary dependencies and tools are installed in the development environment.

Step 2: Configuration initialization

Perform basic configuration according to project requirements.

Step 3: Using core features

Implement the core features according to the example code.

Step 4: Test verification

Run tests to ensure the functionality works properly.

Step 5: Deployment and go-live

After development is complete, proceed with deployment and monitoring.