When to use this skill
ALWAYS use this skill when the user mentions:
- Day-to-day Tauri v2 development workflow
- Dev server vs static assets switching
- Debugging Rust + WebView
- Sidecar or resources management
- Testing strategies for Tauri apps
Trigger phrases include:
- "dev workflow", "debug", "sidecar", "resources", "icons"
- "Development workflow", "debugging", "sidecar", "resource management", "icons"
How to use this skill
- Choose dev server or static asset mode
- Configure resources, sidecar, and icons
- Set up Rust + WebView debugging flow
- Recommend testing strategy (mocking, WebDriver, CI)
Outputs
- Development checklist
- Debugging workflow guide
- Testing recommendations
Scope
- Boundary: Development workflow only
- Key points: Dev server vs static assets and dual-side debugging
- Out of scope: release builds or distribution
References
- https://v2.tauri.app/llms.txt
- https://v2.tauri.app/develop/
- https://v2.tauri.app/develop/configuration-files/
- https://v2.tauri.app/develop/calling-rust/
- https://v2.tauri.app/develop/calling-frontend/
- https://v2.tauri.app/develop/resources/
- https://v2.tauri.app/develop/sidecar/
- https://v2.tauri.app/develop/state-management/
- https://v2.tauri.app/develop/updating-dependencies/
- https://v2.tauri.app/develop/icons/
- https://v2.tauri.app/develop/debug/
- https://v2.tauri.app/develop/debug/crabnebula-devtools/
- https://v2.tauri.app/develop/debug/neovim/
- https://v2.tauri.app/develop/debug/rustrover/
- https://v2.tauri.app/develop/debug/vscode/
- https://v2.tauri.app/develop/plugins/
- https://v2.tauri.app/develop/plugins/develop-mobile/
- https://v2.tauri.app/develop/tests/
- https://v2.tauri.app/develop/tests/mocking/
- https://v2.tauri.app/develop/tests/webdriver/
- https://v2.tauri.app/develop/tests/webdriver/ci/
- https://v2.tauri.app/develop/tests/webdriver/example/selenium/
- https://v2.tauri.app/develop/tests/webdriver/example/webdriverio/
Keywords
tauri develop, dev server, static assets, sidecar, debugging, tests, development workflow, debugging, resource management
Common Pitfalls (Gotchas)
- Version compatibility: Pay attention to compatibility between framework versions 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 your editor's syntax checking
- Environment variables: Ensure all necessary environment variables are set correctly, and do not hard-code sensitive information
- Dependency conflicts: When multiple versions coexist, watch out for dependency conflicts; use lock files 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 development environment has the necessary dependencies and tools installed.
Step 2: Configuration initialization
Perform basic configuration according to project requirements.
Step 3: Using core features
Implement the core functionality according to the example code.
Step 4: Test verification
Run tests to ensure the functionality works properly.
Step 5: Deployment and launch
After development is complete, proceed with deployment and monitoring.