When to use this skill
ALWAYS use this skill when the user mentions:
- Persisting plugin scopes across sessions
- Scope expiration or revocation
- Re-authorization workflow
Trigger phrases include:
- "persisted scope", "expiration", "revocation", "re-authorization"
- "Persistent permissions", "expiration", "revocation", "re-authorization"
How to use this skill
- Define which scopes can be persisted and for how long
- Configure persisted-scope plugin capabilities
- Implement expiration, revocation, and re-approval flows
- Validate scope restoration and downgrade handling
Outputs
- Scope persistence policy
- Expiration and revocation checklist
Scope
- Boundary: Persisted-scope plugin usage only
- Key points: Avoid permanent over-privilege
References
- https://v2.tauri.app/llms.txt
- https://v2.tauri.app/plugin/persisted-scope/
- https://v2.tauri.app/zh-cn/plugin/persisted-scope/
Keywords
tauri persisted scope, permissions, expiration, security
Common Gotchas
- Version compatibility: Pay attention to compatibility between the framework version and dependency libraries; APIs may differ across versions
- Configuration file format: Configuration file format errors are the most common issue; it is recommended to use the editor's syntax checking
- Environment variables: Ensure all necessary environment variables are set correctly, and do not hardcode sensitive information
- Dependency conflicts: Pay attention to dependency conflicts when multiple versions coexist, and use a lock file to pin versions
- Performance pitfalls: Pay attention to performance optimization in large-data scenarios, and avoid common issues such as N+1 queries
Usage workflow
Step 1: Environment preparation
Ensure 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 release
After completing development, proceed with deployment and monitoring.