tauri-app-dialog

When to use this skill

• Native alert, confirm, or file dialogs
• Unified dialog APIs across platforms
• Async dialog flows with cancellation

• "dialog", "alert", "confirm", "file picker", "native dialog"
• "dialog box", "alert box", "confirmation box", "file selection"

How to use this skill

1. Define dialog types and UI flows
2. Configure dialog plugin capabilities and scope
3. Implement async dialog calls and cancellation handling
4. Provide a unified dialog service layer for reuse

Outputs

• Dialog Service Design
• Async and Cancellation Flow Checklist

Scope

• Boundary: Dialog plugin usage only
• Key points: Async behavior and platform consistency

References

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

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: Pay attention to 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 Flow

Step 1: Environment Preparation

Step 2: Configuration Initialization

Step 3: Core Function Usage

Step 4: Testing and Verification

Step 5: Deployment and Launch