UI Debug Agent

Inspect web and mobile UIs to identify stable element locators and debug automation failures.

129|51|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/anhtester/antigravity-testing-kit --skill ui-debug-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: UI Debug Agent
Source: https://github.com/anhtester/antigravity-testing-kit/tree/main/.agent/skills/ui_debug_agent
Command: npx skills add https://github.com/anhtester/antigravity-testing-kit --skill ui-debug-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The UI Debug Agent eliminates uncertainty in UI automation by inspecting live web and mobile pages to identify stable locators, capture DOM structure, and diagnose failures such as element-not-found, click interception, or timing issues.

Core Features & Use Cases

  • Live Inspection & Snapshots: Open a real browser, navigate, resize viewport, wait for load, and capture accessibility-tree snapshots for reliable DOM analysis.
  • Locator Discovery & Verification: Recommend prioritized locators for Playwright, Selenium, and Appium, verify uniqueness and stability, and validate by interacting with snapshot refs.
  • Debugging & Evidence Collection: Diagnose iframe, shadow DOM, and dynamic SPA issues, provide root-cause findings and fixes for automation failures, capture screenshots for reports, and suggest Page Object class structures.
  • Use Case: When a login test starts failing after a UI change, run the Skill to snapshot the page, locate a robust selector for the login button, verify it across reloads, and generate patch recommendations for test scripts.

Quick Start

Ask the UI Debug Agent to inspect https://example.com/login, take a snapshot, and return verified Playwright and Selenium locators for the primary login button.

Frequently Asked Questions about UI Debug Agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find stable UI locators when my Playwright or Selenium tests keep failing?

To find stable UI locators, inspect the live page to capture accessibility-tree snapshots and verify prioritized selectors across Playwright, Selenium, and Appium. This process diagnoses element-not-found and click-intercepted errors by validating locator uniqueness against the live DOM structure.

What is the best way to debug element-not-found errors in dynamic single-page applications?

Debugging element-not-found errors in SPAs involves capturing DOM analysis and accessibility-tree snapshots to identify root causes like timing issues or dynamic content shifts. It provides root-cause findings and patch recommendations to fix failing automation scripts.

How do I inspect elements inside a shadow DOM or iframe for test automation?

Inspecting elements inside a shadow DOM or iframe requires capturing accessibility-tree snapshots that pierce these boundaries to analyze the underlying DOM. This snapshot verifies locators and diagnoses structural failures for automation frameworks.

Does this UI inspection approach work with Appium for mobile views?

Yes, this UI inspection approach works with Appium to inspect mobile views and identify stable element locators. It captures snapshots of mobile UIs, verifies locator uniqueness, and applies locator priority rules to debug mobile automation failures.

How do I generate Page Object recommendations after verifying my UI locators?

To generate Page Object recommendations, verify your UI locators across reloads and frameworks, then translate the validated selectors into suggested Page Object class structures. This provides structured code recommendations for your test scripts.

Why does my automated click get intercepted, and how can DOM analysis fix it?

An automated click gets intercepted when another element overlays the target, which DOM analysis identifies by inspecting the live accessibility tree. Capturing screenshots and snapshots diagnoses the overlay issue and recommends stable locators to resolve the failure.