/click
Send a mouse click to specific coordinates in a Tauri application window
$ 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
/click
Context preview
What this command does when you run it.
Send a mouse click to specific coordinates in a Tauri application window
Command definition
click.mdname: rust:tauri:click
description: Send a mouse click to specific coordinates in a Tauri application window
allowed-tools: mcp__tauri-mcp__send_mouse_click, mcp__tauri-mcp__take_screenshot, mcp__tauri-mcp__get_window_info
author: Quintin Henry (https://github.com/qdhenry/)
<objective> Send a mouse click event to a specific position in a Tauri application window. Useful for UI automation and testing. </objective>
<instructions> Send mouse click to the Tauri application: **$ARGUMENTS**
Arguments format: `[process_id] [x] [y] [--button left|right|middle]`
- `process_id`: Required - the process ID from `/tauri:launch`
- `x`: Required - X coordinate (pixels from left edge)
- `y`: Required - Y coordinate (pixels from top edge)
- `--button`: Optional - mouse button (default: left)
Process
1. **Verify Window State** Use `mcp__tauri-mcp__get_window_info` to confirm window is visible and focused.
2. **Take Pre-Click Screenshot** (if helpful) Capture state before the click for debugging.
3. **Send the Click** Use `mcp__tauri-mcp__send_mouse_click` with:
- `process_id`: Target process
- `x`: X coordinate
- `y`: Y coordinate
- `button`: "left", "right", or "middle"
4. **Verify Result** Optionally take a post-click screenshot to confirm the action worked.
Usage Examples
# Left click at coordinates
/tauri:click 12345 100 200
# Right click (context menu)
/tauri:click 12345 100 200 --button right
# Click a specific button (find coords from screenshot first)
/tauri:screenshot 12345
# Identify button at (150, 300)
/tauri:click 12345 150 300
</instructions>
<output_format>
=== Mouse Click Sent ===
Process: [PID]
Position: ([x], [y])
Button: [left/right/middle]
Window Size: [width]x[height]
Click Within Bounds: [yes/no]
</output_format>
<workflow_tip> **Finding Coordinates:** 1. Take a screenshot: `/tauri:screenshot [pid]` 2. Open the image and identify the target element 3. Note the approximate x,y coordinates 4. Send the click: `/tauri:click [pid] [x] [y]` 5. Verify with another screenshot
**For Repeated Testing:** Consider using `/tauri:exec-js` to click elements by selector instead:
document.querySelector('#my-button').click()</workflow_tip>
<troubleshooting> **Click doesn't register:**
- Verify coordinates are within window bounds
- Ensure window is focused and visible
- Try clicking center of element, not edges
**Wrong element clicked:**
- Take a fresh screenshot to verify current state
- Remember coordinates are relative to window, not screen
</troubleshooting>
Read more
name: rust:tauri:click description: Send a mouse click to specific coordinates in a Tauri application window allowed-tools: mcp__tauri-mcp__send_mouse_click, mcp__tauri-mcp__take_screenshot, mcp__tauri-mcp__get_window_info author: Quintin Henry (https://github.com/qdhenry/)
<objective> Send a mouse click event to a specific position in a Tauri application window. Useful for UI automation and testing. </objective>
<instructions> Send mouse click to the Tauri application: **$ARGUMENTS**
Arguments format: `[process_id] [x] [y] [--button left|right|middle]`
- `process_id`: Required - the process ID from `/tauri:launch`
- `x`: Required - X coordinate (pixels from left edge)
- `y`: Required - Y coordinate (pixels from top edge)
- `--button`: Optional - mouse button (default: left)
Process
1. **Verify Window State** Use `mcp__tauri-mcp__get_window_info` to confirm window is visible and focused.
2. **Take Pre-Click Screenshot** (if helpful) Capture state before the click for debugging.
3. **Send the Click** Use `mcp__tauri-mcp__send_mouse_click` with:
- `process_id`: Target process
- `x`: X coordinate
- `y`: Y coordinate
- `button`: "left", "right", or "middle"
4. **Verify Result** Optionally take a post-click screenshot to confirm the action worked.
Usage Examples
# Left click at coordinates /tauri:click 12345 100 200 # Right click (context menu) /tauri:click 12345 100 200 --button right # Click a specific button (find coords from screenshot first) /tauri:screenshot 12345 # Identify button at (150, 300) /tauri:click 12345 150 300
</instructions>
<output_format>
=== Mouse Click Sent === Process: [PID] Position: ([x], [y]) Button: [left/right/middle] Window Size: [width]x[height] Click Within Bounds: [yes/no]
</output_format>
<workflow_tip> **Finding Coordinates:** 1. Take a screenshot: `/tauri:screenshot [pid]` 2. Open the image and identify the target element 3. Note the approximate x,y coordinates 4. Send the click: `/tauri:click [pid] [x] [y]` 5. Verify with another screenshot
**For Repeated Testing:** Consider using `/tauri:exec-js` to click elements by selector instead:
document.querySelector('#my-button').click()</workflow_tip>
<troubleshooting> **Click doesn't register:**
- Verify coordinates are within window bounds
- Ensure window is focused and visible
- Try clicking center of element, not edges
**Wrong element clicked:**
- Take a fresh screenshot to verify current state
- Remember coordinates are relative to window, not screen
</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

