/devtools
Get DevTools connection information for debugging a Tauri application
$ npx -y skills add qdhenry/Claude-Command-Suite --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/devtools
Context preview
What this command does when you run it.
Get DevTools connection information for debugging a Tauri application
Command definition
devtools.mdname: rust:tauri:devtools
description: Get DevTools connection information for debugging a Tauri application
allowed-tools: mcp__tauri-mcp__get_devtools_info
author: Quintin Henry (https://github.com/qdhenry/)
<objective> Retrieve DevTools connection information for a running Tauri application, enabling browser-based debugging of the webview. </objective>
<instructions> Get DevTools info for the Tauri application: **$ARGUMENTS**
Arguments: `[process_id]`
Process
1. **Query DevTools Information** Use `mcp__tauri-mcp__get_devtools_info` with the process ID.
2. **Provide Connection Instructions** Show how to connect to DevTools for debugging.
Usage Examples
# Get DevTools connection info
/tauri:devtools 12345
</instructions>
<output_format>
=== DevTools Information ===
Process ID: [PID]
--- Connection ---
Debug Port: [port]
WebSocket URL: [ws://...]
HTTP URL: [http://...]
--- How to Connect ---
1. Open Chrome/Edge browser
2. Navigate to: chrome://inspect
3. Click "Configure..." and add: localhost:[port]
4. Your app should appear under "Remote Target"
5. Click "inspect" to open DevTools
--- Alternative ---
Direct URL: [devtools://devtools/bundled/inspector.html?ws=...]
</output_format>
<debugging_tips> **What You Can Do with DevTools:**
- Inspect DOM elements and styles
- Debug JavaScript with breakpoints
- Monitor network requests
- Profile performance
- View console logs and errors
- Inspect localStorage/sessionStorage
**Common Debug Tasks:**
- Check for JavaScript errors in Console
- Inspect React components (with React DevTools)
- Monitor Tauri IPC calls in Network tab
- Profile rendering performance
</debugging_tips>
Read more
name: rust:tauri:devtools description: Get DevTools connection information for debugging a Tauri application allowed-tools: mcp__tauri-mcp__get_devtools_info author: Quintin Henry (https://github.com/qdhenry/)
<objective> Retrieve DevTools connection information for a running Tauri application, enabling browser-based debugging of the webview. </objective>
<instructions> Get DevTools info for the Tauri application: **$ARGUMENTS**
Arguments: `[process_id]`
Process
1. **Query DevTools Information** Use `mcp__tauri-mcp__get_devtools_info` with the process ID.
2. **Provide Connection Instructions** Show how to connect to DevTools for debugging.
Usage Examples
# Get DevTools connection info /tauri:devtools 12345
</instructions>
<output_format>
=== DevTools Information === Process ID: [PID] --- Connection --- Debug Port: [port] WebSocket URL: [ws://...] HTTP URL: [http://...] --- How to Connect --- 1. Open Chrome/Edge browser 2. Navigate to: chrome://inspect 3. Click "Configure..." and add: localhost:[port] 4. Your app should appear under "Remote Target" 5. Click "inspect" to open DevTools --- Alternative --- Direct URL: [devtools://devtools/bundled/inspector.html?ws=...]
</output_format>
<debugging_tips> **What You Can Do with DevTools:**
- Inspect DOM elements and styles
- Debug JavaScript with breakpoints
- Monitor network requests
- Profile performance
- View console logs and errors
- Inspect localStorage/sessionStorage
**Common Debug Tasks:**
- Check for JavaScript errors in Console
- Inspect React components (with React DevTools)
- Monitor Tauri IPC calls in Network tab
- Profile rendering performance
</debugging_tips>
A comprehensive development toolkit designed following Anthropic's Claude Code Best Practices for AI-assisted software development.
Repo: qdhenry/Claude-Command-Suite
Other commands on claude-command-suite.
- /boundary-bbcr-fallback
Execute automatic BBCR (Collapse-Rebirth Correction) when knowledge boundaries are exceeded or reasoning fails.
Open command - /boundary-detect
Analyze semantic position relative to knowledge boundaries to prevent hallucination and identify uncertainty zones.
Open command - /boundary-heatmap
Generate a visual heatmap of knowledge boundaries showing safe zones, risk areas, and semantic coverage.
Open command - /boundary-risk-assess
Evaluate the current risk level and provide detailed analysis of potential hallucination or reasoning failure.
Open command - /boundary-safe-bridge
Find and construct semantic bridges to safely navigate from current position to target concept without crossing dangerous boundaries.
Open command - /optimize-prompt
Takes an input prompt and returns ONLY a token-optimized version that preserves meaning while minimizing token count. Based on LLM tokenization principles: common words tokenize more efficiently, unusual words break into more tokens, and conciseness reduces cost.
Open command

