When to use this skill
ALWAYS use this skill when the user mentions:
- Tauri v2 security baseline, hardening, or audit
- CSP, HTTP headers, or runtime authority
- Capability/Scope design for security posture
Trigger phrases include:
- "security baseline", "hardening", "CSP", "security checklist"
- "security baseline", "security hardening", "permission convergence", "release audit"
How to use this skill
- Clarify app context: platforms, windows, data sensitivity
- Build a capability matrix: feature → plugin → capability → scope
- Define CSP and HTTP headers per window
- Review runtime authority and plugin permissions
- Produce a release security checklist and validation plan
Outputs
- Capability matrix with minimal scope
- CSP & headers plan per window
- Release security checklist
Scope
- Boundary: Tauri v2 security model and baseline hardening
- In scope: Capabilities, Scope, CSP, headers, runtime authority
- Out of scope: backend auth or server security
References
- https://v2.tauri.app/security/
- https://v2.tauri.app/security/permissions/
- https://v2.tauri.app/security/scope/
- https://v2.tauri.app/security/capabilities/
- https://v2.tauri.app/security/csp/
- https://v2.tauri.app/security/http-headers/
- https://v2.tauri.app/security/ecosystem/
- https://v2.tauri.app/security/lifecycle/
- https://v2.tauri.app/security/future/
- https://v2.tauri.app/security/runtime-authority/
Keywords
tauri security, csp, headers, permissions, capabilities, runtime authority, security baseline, permission convergence, runtime authority