ui-automation-workflows
Accessibility-first UI automation using IDB. Query accessibility tree (fast, 50 tokens) before screenshots (slow, 170 tokens). Use when automating simulator interactions, tapping UI elements, finding buttons, or testing user flows. Covers idb-ui-describe, idb-ui-tap, idb-ui-find-element patterns.
Install
With your agent
Install OMGSkills skill "conorluddy/xclaude-plugin:skills/ui-automation-workflows" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/conorluddy/xclaude-plugin /tmp/xclaude-plugin && ln -s /tmp/xclaude-plugin/skills/ui-automation-workflows ~/.claude/skills/ui-automation-workflowsFrom README
UI Automation Workflows Use the executeidbcommand MCP tool for all UI automation The xclaude-plugin provides the executeidbcommand MCP tool which consolidates all IDB UI automation operations into a single, token-efficient dispatcher. ⚠️ CRITICAL: Always Use MCP Tools First This is the most important rule: When automating UI interactions, you MUST use the executeidbcommand MCP tool. ✅ DO: Invoke executeidbcommand for all UI automation, element finding, and accessibility queries ✅ DO: If the MCP tool fails, adjust parameters and retry ✅ DO: Read error messages and debug the parameters ❌ NEVER: Fall back to bash idb commands ❌ NEVER: Use idb directly in bash ❌ NEVER: Run idb commands in a terminal Why? The MCP tool provides: Structured error handling Token efficiency (consolidated into 1 tool vs.
More from this repo
crash-debugging
Crash log analysis, symbolication, and debugging workflows for iOS apps.
ios-testing-patterns
XCTest and XCUITest execution workflows and flaky test detection patterns
performance-profiling
Instruments integration and performance analysis workflows for iOS apps.