tauri-security

Original：🇨🇳 Chinese

Translated

Guidance for Tauri v2 capabilities, scope configuration, and ACL-based permission control.

3installs

Sourcefull-stack-skills/tauri-skills

Added on2026-11-09

NPX Install

npx skill4agent add full-stack-skills/tauri-skills tauri-security

SKILL.md Content (Chinese)

View Translation Comparison →

When to use this skill

ALWAYS use this skill when the user mentions:

Capability/Scope design or ACL permission control
Building or validating capabilities/default.json
Tightening plugin access in production

Trigger phrases include:

"capabilities", "scope", "acl", "permissions file"
"permission configuration", "capability file", "scope configuration", "ACL"

How to use this skill

Translate features into plugin capabilities
Define scoped access rules per capability
Generate and validate capabilities/default.json
Verify runtime behavior matches the minimum-privilege policy

Outputs

Capability-to-scope mapping
Validated capabilities/default.json
Permission audit checklist

Scope

Boundary: Capabilities, scope, and ACL configuration only
v2 focus: Capabilities and scope are mandatory controls
Out of scope: App feature design or backend auth

References

Keywords

tauri security, capabilities, scope, acl, permissions, permission configuration, capability files, least privilege

Common Gotchas

Version compatibility: Pay attention to compatibility between framework versions and dependencies; APIs may differ between versions.
Configuration file format: Invalid configuration file syntax is the most common issue; use an editor with syntax checking.
Environment variables: Ensure all required environment variables are correctly set, and do not hardcode sensitive information.
Dependency conflicts: Watch for dependency conflicts when multiple versions coexist, and use a lock file to pin versions.
Performance pitfalls: Optimize performance in large-data scenarios and avoid common issues such as N+1 queries.

Workflow

Step 1: Environment Setup

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

Step 2: Configuration Initialization

Perform the initial configuration according to the project requirements.

Step 3: Core Feature Implementation

Implement the core functionality by following the sample code.

Step 4: Testing and Validation

Run tests to ensure that the functionality works as expected.

Step 5: Deployment

Complete deployment and monitoring after development.