inspecting-zeus-desktop-dom

Inspect the live ZeusAgent desktop DOM and computed CSS over the Chrome DevTools Protocol.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/loteiron/ZeusAgent --skill inspecting-zeus-desktop-dom-loteiron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: inspecting-zeus-desktop-dom
Source: https://github.com/loteiron/ZeusAgent/tree/main/skills/software-development/inspecting-zeus-desktop-dom
Command: npx skills add https://github.com/loteiron/ZeusAgent --skill inspecting-zeus-desktop-dom-loteiron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When developing the ZeusAgent desktop app, inferring rendered UI state from .tsx source files leads to wrong conclusions. This Skill reads the live rendered DOM of the running Electron window — computed styles, geometry, winning CSS rules, and console output — over the Chrome DevTools Protocol port exposed by dev-server runs. ## Core Features & Use Cases - Live DOM and computed style reading: Query the running renderer via apps/desktop/scripts/eval.mjs or the shared CDP client with target discovery and promise-aware eval. - CSS rule resolution: Determine which selector actually won on a real node, including inherited values and plugin stylesheet overrides, before editing call sites. - Isolated probe instances: Launch a separate Electron instance with its own ZEUS_HOME, user-data-dir, and CDP port so the user's session is never disturbed. - Use Case: A style change "isn't applying" in the running app. Instead of sweeping every call site, evaluate the real node, see that the value is inherited from an ancestor rule set by @tailwindcss/typography, and override the shared class once. ## Quick Start Ask the agent to check the CDP port on 127.0.0.1:9222 and read the computed style of a specific element in the running ZeusAgent desktop window.

Frequently Asked Questions about inspecting-zeus-desktop-dom

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

FAQPage Schema
How do I inspect the DOM of a running Electron app?▼

Electron dev-server runs expose a Chrome DevTools Protocol port on 127.0.0.1:9222. Verify it with curl to /json/version, then evaluate expressions against the renderer using apps/desktop/scripts/eval.mjs or the shared CDP client in scripts/perf/lib/cdp.mjs.

How do I find which CSS rule is styling an element?▼

Query the real node in the live renderer and read its computed style plus ancestor classes. If the node carries no class of its own, the value is inherited, so override the ancestor or shared class rather than editing each call site.

Why is the CDP port not open on 127.0.0.1:9222?▼

The port is closed for packaged builds and for unpackaged runs without ZEUS_DESKTOP_DEV_SERVER set. ZEUS_DESKTOP_CDP_PORT can move the port or disable it entirely with the value off.

Can I inspect the desktop app without disturbing the user's session?▼

Yes. Launch an isolated Electron instance with a separate ZEUS_HOME, --user-data-dir, and a different CDP port such as 9333. This avoids the single-instance lock and keeps the probe away from real sessions.

What are the limitations of CDP-based DOM inspection?▼

CDP answers factual questions like computed padding or whether an element rendered, but cannot judge aesthetics such as colour balance or spacing feel. It also does not cover performance profiling or heap analysis, which need dedicated debugging tools.