/launch
Launch a Tauri desktop application and return its process ID for subsequent operations
$ 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
/launch
Context preview
What this command does when you run it.
Launch a Tauri desktop application and return its process ID for subsequent operations
Command definition
launch.mdname: rust:tauri:launch
description: Launch a Tauri desktop application and return its process ID for subsequent operations
allowed-tools: mcp__tauri-mcp__launch_app, mcp__tauri-mcp__get_app_logs, mcp__tauri-mcp__get_window_info, Bash, Read
author: Quintin Henry (https://github.com/qdhenry/)
<objective> Launch a Tauri desktop application and prepare it for interaction. Returns the process ID needed for all subsequent tauri commands. </objective>
<context> Project Tauri app location: !`ls -la apps/desktop/src-tauri/target/release/*.app 2>/dev/null || ls -la apps/desktop/src-tauri/target/debug/*.app 2>/dev/null || echo "No built app found - run 'bun run build' in apps/desktop first"` Current running apps: !`pgrep -l -f "tauri\|monotask" 2>/dev/null || echo "No Tauri apps currently running"` </context>
<instructions> Launch the Tauri application: **$ARGUMENTS**
If no path is provided, attempt to find and launch the project's desktop app.
Launch Process
1. **Determine App Path**
- If `$ARGUMENTS` contains a path, use that
- Otherwise, look for built app in `apps/desktop/src-tauri/target/`
- Prefer release build over debug build
2. **Launch the Application** Use `mcp__tauri-mcp__launch_app` with:
- `app_path`: Path to the .app bundle (macOS) or executable
- `args`: Optional launch arguments (e.g., `["--dev"]`)
3. **Wait for Startup** After launching, wait 2-3 seconds for the app to initialize.
4. **Verify Launch Success**
- Use `mcp__tauri-mcp__get_window_info` to confirm window is visible
- Use `mcp__tauri-mcp__get_app_logs` to check for startup errors
5. **Report Results** Provide:
- Process ID (required for all subsequent commands)
- Window dimensions and state
- Any startup logs or errors
Usage Examples
# Launch project's desktop app
/tauri:launch
# Launch specific app
/tauri:launch /Applications/MyTauriApp.app
# Launch with arguments
/tauri:launch apps/desktop/src-tauri/target/release/bundle/macos/Monotask.app --dev
</instructions>
<output_format> Provide a concise summary:
App Launched Successfully
- Process ID: [PID]
- Window: [width]x[height] at ([x], [y])
- Status: [visible/minimized/etc]
Use this process_id for subsequent /tauri: commands.
Or if launch failed:
Launch Failed
- Error: [error message]
- Suggestion: [how to fix]
</output_format>
<troubleshooting> **"No built app found":**
- Run `cd apps/desktop && bun run build` to build the app first
- For dev testing, use `bun run dev` instead and interact via browser
**"Permission denied":**
- On macOS, you may need to allow the app in System Preferences > Security
- Run `xattr -cr /path/to/app.app` to clear quarantine flags
**App launches but window doesn't appear:**
- Check logs for initialization errors
- Verify display/screen configuration
- Some apps need specific environment variables
</troubleshooting>
Read more
name: rust:tauri:launch description: Launch a Tauri desktop application and return its process ID for subsequent operations allowed-tools: mcp__tauri-mcp__launch_app, mcp__tauri-mcp__get_app_logs, mcp__tauri-mcp__get_window_info, Bash, Read author: Quintin Henry (https://github.com/qdhenry/)
<objective> Launch a Tauri desktop application and prepare it for interaction. Returns the process ID needed for all subsequent tauri commands. </objective>
<context> Project Tauri app location: !`ls -la apps/desktop/src-tauri/target/release/*.app 2>/dev/null || ls -la apps/desktop/src-tauri/target/debug/*.app 2>/dev/null || echo "No built app found - run 'bun run build' in apps/desktop first"` Current running apps: !`pgrep -l -f "tauri\|monotask" 2>/dev/null || echo "No Tauri apps currently running"` </context>
<instructions> Launch the Tauri application: **$ARGUMENTS**
If no path is provided, attempt to find and launch the project's desktop app.
Launch Process
1. **Determine App Path**
- If `$ARGUMENTS` contains a path, use that
- Otherwise, look for built app in `apps/desktop/src-tauri/target/`
- Prefer release build over debug build
2. **Launch the Application** Use `mcp__tauri-mcp__launch_app` with:
- `app_path`: Path to the .app bundle (macOS) or executable
- `args`: Optional launch arguments (e.g., `["--dev"]`)
3. **Wait for Startup** After launching, wait 2-3 seconds for the app to initialize.
4. **Verify Launch Success**
- Use `mcp__tauri-mcp__get_window_info` to confirm window is visible
- Use `mcp__tauri-mcp__get_app_logs` to check for startup errors
5. **Report Results** Provide:
- Process ID (required for all subsequent commands)
- Window dimensions and state
- Any startup logs or errors
Usage Examples
# Launch project's desktop app /tauri:launch # Launch specific app /tauri:launch /Applications/MyTauriApp.app # Launch with arguments /tauri:launch apps/desktop/src-tauri/target/release/bundle/macos/Monotask.app --dev
</instructions>
<output_format> Provide a concise summary:
App Launched Successfully - Process ID: [PID] - Window: [width]x[height] at ([x], [y]) - Status: [visible/minimized/etc] Use this process_id for subsequent /tauri: commands.
Or if launch failed:
Launch Failed - Error: [error message] - Suggestion: [how to fix]
</output_format>
<troubleshooting> **"No built app found":**
- Run `cd apps/desktop && bun run build` to build the app first
- For dev testing, use `bun run dev` instead and interact via browser
**"Permission denied":**
- On macOS, you may need to allow the app in System Preferences > Security
- Run `xattr -cr /path/to/app.app` to clear quarantine flags
**App launches but window doesn't appear:**
- Check logs for initialization errors
- Verify display/screen configuration
- Some apps need specific environment variables
</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

