tauri-security

When to use this skill

ALWAYS use this skill when the user mentions:

• Capability/Scope design or ACL permission control / Capability, Scope, ACL permission control
• Building capabilities/default.json / Generate or validate capabilities/default.json
• Tightening plugin access in production / Production environment permission tightening

Trigger phrases include:

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

How to use this skill

1. Translate features into plugin capabilities / Map business features to plugin capabilities
2. Define scoped access rules per capability / Define Scope rules for capabilities
3. Generate and validate capabilities/default.json / Generate and validate the capability file
4. Verify runtime behavior matches minimum-privilege policy / Verify the minimum-privilege runtime effect

Outputs

• Capability-to-scope mapping / Mapping from capabilities to Scope
• Validated capabilities/default.json / Ready-to-use capability file
• Permission audit checklist / Permission audit checklist

Scope

• Boundary: Capabilities, scope, and ACL configuration only / Permission configuration only
• v2 focus: Capabilities & scope are mandatory controls / Mandatory configuration in v2
• Out of scope: app feature design or backend auth / Does not include feature design and backend authentication

References

• https://v2.tauri.app/security/capabilities/
• https://v2.tauri.app/security/scope/
• https://v2.tauri.app/security/acl/

Keywords

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