菜单
Tauri 2 end-to-end debugging workflow that chooses between official baseline tools, CrabNebula DevTools, and a live MCP bridge. Use when debugging is ambiguous or spans frontend UI, Rust commands, IPC, logs, and runtime state together.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use CrabNebula DevTools for Tauri 2 Rust-side debugging, IPC analysis, tracing spans, config inspection, and command/event timing. Trigger when browser devtools are insufficient because the issue involves Rust commands, permissions, capability bundles, spans, logs, or backend performance.
Use the Hypothesi Tauri MCP server and tauri-plugin-mcp-bridge to let an agent inspect and drive a live Tauri 2 app. Trigger when debugging needs screenshots, DOM snapshots, clicks, typing, JS execution, window management, logs, or real-time IPC monitoring.
Official Tauri 2 debugging baseline for desktop and mobile apps. Use when debugging any Tauri v2 issue before heavier tooling, especially for WebView errors, Rust panics, missing logs, devtools access, debug builds, LLDB/GDB workflows, or plugin-log setup.
| name | tauri-unified-debug-workflow |
| description | Tauri 2 end-to-end debugging workflow that chooses between official baseline tools, CrabNebula DevTools, and a live MCP bridge. Use when debugging is ambiguous or spans frontend UI, Rust commands, IPC, logs, and runtime state together. |
Use this skill to choose the right tool instead of jumping straight into random instrumentation.
tauri devRUST_BACKTRACE=1 tauri dev if Rust crashesWhen using this workflow, always summarize: