tauri-app-single-instance

When to use this skill

• Preventing multiple app instances
• Handling second-launch arguments
• Deep-linking or CLI integration with single-instance

• "single instance", "second launch", "arguments", "deep linking"

How to use this skill

1. Enable single-instance and define init behavior
2. Capture and route second-launch arguments to the app
3. Focus or restore the main window on re-entry
4. Validate behavior with deep-linking or CLI scenarios

Outputs

• Single-instance behavior plan
• Second-launch routing checklist

Scope

• Boundary: Single-instance configuration and runtime behavior
• Key points: Safe argument passing and window focus behavior

References

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

Keywords

Gotchas

1. Version Compatibility: Pay attention to compatibility between framework versions and dependent libraries; APIs may vary across different versions
2. Configuration File Format: Incorrect configuration file format is the most common issue; it is recommended to use the editor's syntax checking
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 scenarios; avoid common issues such as N+1 queries

Usage Workflow

Step 1: Environment Preparation

Step 2: Initial Configuration

Step 3: Core Function Usage

Step 4: Testing and Validation

Step 5: Deployment and Launch