tauri-app-persisted-scope
When to use this skill
ALWAYS use this skill when the user mentions:
- Persisting plugin scopes across app restarts
- Remembering file access permissions between sessions
- Scope expiration or revocation flows
Trigger phrases include:
- "persisted scope", "remember access", "scope persistence", "re-authorization", "scope expiration"
How to use this skill
- Install the persisted-scope plugin:
cargo add tauri-plugin-persisted-scope - Register the plugin in your Tauri builder:
tauri::Builder::default() .plugin(tauri_plugin_persisted_scope::init()) - Configure capabilities in
src-tauri/capabilities/default.json:{ "permissions": ["persisted-scope:allow-save", "persisted-scope:allow-load"] } - How it works: When the user grants file access (e.g., via a dialog picker), the persisted-scope plugin automatically saves those scope entries to disk and restores them on next launch
- Implement expiration by periodically checking saved scopes and removing stale entries
- Add revocation UI to let users manage which persistent access grants remain active
- Avoid permanent over-privilege by reviewing persisted scopes during app startup
Outputs
- Persisted scope plugin setup for cross-session access retention
- Expiration and revocation flow patterns
- Scope audit guidance to prevent over-privilege
References
Keywords
tauri persisted scope, scope persistence, file access, re-authorization, expiration
More from partme-ai/full-stack-skills
vite
Guidance for Vite using the official Guide, Config Reference, and Plugins pages. Use when the user needs Vite setup, configuration, or plugin selection details.
68element-plus-vue3
Provides comprehensive guidance for Element Plus Vue 3 component library including installation, components, themes, internationalization, and API reference. Use when the user asks about Element Plus for Vue 3, needs to build Vue 3 applications with Element Plus, or customize component styles.
64vue3
Guidance for Vue 3 using the official guide and API reference. Use when the user needs Vue 3 concepts, patterns, or API details to build components, apps, and tooling.
54electron
Build cross-platform desktop applications with Electron, covering main/renderer process architecture, IPC communication, BrowserWindow management, menus, tray icons, packaging, and security best practices. Use when the user asks about Electron, needs to create desktop applications, implement Electron features, or build cross-platform desktop apps.
52uniapp-project
Provides per-component and per-API examples with cross-platform compatibility details for uni-app, covering built-in components, uni-ui components, and APIs (network, storage, device, UI, navigation, media). Use when the user needs official uni-app components or APIs, wants per-component examples with doc links, or needs platform compatibility checks.
40ascii-cli-logo-banner
Entry point for ASCII CLI banners that routes to the Python built-in font skill or figlet.js/FIGfont skill. Use when the user wants a startup banner, ASCII logo, terminal welcome screen, or CLI branding for a service.
38