Debug Tauri DevTools

Use CrabNebula DevTools for the part of a Tauri app that browser DevTools cannot see: Rust-side logs, IPC spans, resolved runtime config, capability state, plugin wiring, and bundled asset resolution.

Trigger

Activate when the user reports or the agent observes any of these:

• a Tauri invoke() call fails, hangs, is unexpectedly slow, or returns wrong data
• a Rust panic/error exists but the failing module or span is unclear
• a plugin, capability, or window-scope permission appears broken
• an asset loads in dev but not in build, or exists locally but not in the bundle
• behavior differs across desktop/mobile or debug/build modes
• you are about to add println!(), guess at serde/config issues, or inspect the browser Network tab for Tauri IPC
• CrabNebula DevTools needs to be installed, configured, or is not connecting

When NOT to use this skill