/stop
Stop a running Tauri application by process ID
$ 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
/stop
Context preview
What this command does when you run it.
Stop a running Tauri application by process ID
Command definition
stop.mdname: rust:tauri:stop
description: Stop a running Tauri application by process ID
allowed-tools: mcp__tauri-mcp__stop_app, mcp__tauri-mcp__get_app_logs, Bash
author: Quintin Henry (https://github.com/qdhenry/)
<objective> Gracefully stop a running Tauri application. Captures final logs before termination. </objective>
<context> Running Tauri processes: !`pgrep -l -f "tauri\|monotask" 2>/dev/null || echo "No Tauri apps currently running"` </context>
<instructions> Stop the Tauri application: **$ARGUMENTS**
The argument should be a process ID from a previous `/tauri:launch` command.
Stop Process
1. **Get Final Logs** Before stopping, capture any remaining logs using `mcp__tauri-mcp__get_app_logs`:
- `process_id`: The PID to stop
- `lines`: Last 50 lines
2. **Stop the Application** Use `mcp__tauri-mcp__stop_app` with:
- `process_id`: The process ID to terminate
3. **Verify Termination** Confirm the process has stopped using a quick process check.
4. **Report Results**
- Confirmation of termination
- Any notable final log entries
- Errors if termination failed
Usage Examples
# Stop by process ID
/tauri:stop 12345
# Stop with "process_id" prefix (from copy-paste)
/tauri:stop process_id: 12345
</instructions>
<output_format>
App Stopped Successfully
- Process ID: [PID]
- Final Status: [exit status if available]
Notable final logs:
[any errors or important messages]
</output_format>
<troubleshooting> **"Process not found":**
- The app may have already terminated
- Verify the process ID is correct
- Run `/tauri:launch` to start a new instance
**"Failed to stop":**
- Try `kill -9 [PID]` as a fallback
- Check if the process is zombied
</troubleshooting>
Read more
name: rust:tauri:stop description: Stop a running Tauri application by process ID allowed-tools: mcp__tauri-mcp__stop_app, mcp__tauri-mcp__get_app_logs, Bash author: Quintin Henry (https://github.com/qdhenry/)
<objective> Gracefully stop a running Tauri application. Captures final logs before termination. </objective>
<context> Running Tauri processes: !`pgrep -l -f "tauri\|monotask" 2>/dev/null || echo "No Tauri apps currently running"` </context>
<instructions> Stop the Tauri application: **$ARGUMENTS**
The argument should be a process ID from a previous `/tauri:launch` command.
Stop Process
1. **Get Final Logs** Before stopping, capture any remaining logs using `mcp__tauri-mcp__get_app_logs`:
- `process_id`: The PID to stop
- `lines`: Last 50 lines
2. **Stop the Application** Use `mcp__tauri-mcp__stop_app` with:
- `process_id`: The process ID to terminate
3. **Verify Termination** Confirm the process has stopped using a quick process check.
4. **Report Results**
- Confirmation of termination
- Any notable final log entries
- Errors if termination failed
Usage Examples
# Stop by process ID /tauri:stop 12345 # Stop with "process_id" prefix (from copy-paste) /tauri:stop process_id: 12345
</instructions>
<output_format>
App Stopped Successfully - Process ID: [PID] - Final Status: [exit status if available] Notable final logs: [any errors or important messages]
</output_format>
<troubleshooting> **"Process not found":**
- The app may have already terminated
- Verify the process ID is correct
- Run `/tauri:launch` to start a new instance
**"Failed to stop":**
- Try `kill -9 [PID]` as a fallback
- Check if the process is zombied
</troubleshooting>
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

