tauri-app-store

When to use this skill

• Lightweight persistent storage
• Store vs. LazyStore selection
• Saving app settings to disk

• "store", "lazystore", "persistence", "key-value"
• "persistence", "local storage", "saving settings", "key-value"

How to use this skill

1. Decide between Store and LazyStore based on load timing
2. Define the storage file location and schema
3. Restrict access via capabilities and scope
4. Validate persistence lifecycle and error handling

Outputs

• Store selection guidance
• Persistence plan for app settings

Scope

• Boundary: Store plugin usage only
• Key points: Store vs LazyStore differences

References

• https://v2.tauri.app/llms.txt
• https://v2.tauri.app/plugin/store/
• https://v2.tauri.app/zh-cn/plugin/store/

Keywords

Gotchas

1. Version Compatibility: Pay attention to compatibility between framework versions and dependent libraries; APIs may differ across versions
2. Configuration File Format: Incorrect configuration file format is the most common issue; it is recommended to use the editor's syntax check
3. Environment Variables: Ensure all necessary environment variables are set correctly; do not hardcode sensitive information
4. Dependency Conflicts: Be cautious of dependency conflicts when multiple versions coexist; use lock files to lock versions
5. Performance Pitfalls: Pay attention to performance optimization in large data volume scenarios; avoid common issues such as N+1 queries

Usage Process

Step 1: Environment Preparation

Step 2: Configuration Initialization

Step 3: Core Function Usage

Step 4: Testing and Verification

Step 5: Deployment and Launch