Individual skill

control-ui

Drive and inspect a local web, IDE, or Electron UI with browser or CDP automation and evidence. Use for UI regressions, screenshots, accessibility snapshots, visual diffs, focus, keyboard, scrolling, resize, console, network, performance, or heap checks. Do not use for backend-only changes or for a screenshot without a behavior claim.

skills/development/control-ui/SKILL.md

Read pinned source

Source commit 849719987d9c0d6ed973bdbce8ed37b266d3b1f3

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 214
Repository last updated: Nov 7, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai-agents Repository topic
claude Repository topic
claude-code Repository topic
llm Repository topic
machine-learning Repository topic
prompt-engineering Repository topic
skills Repository topic
mcp Repository topic
agent-harness Repository topic
harness Repository topic
design Derived category
design-interface Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 3,026 bytes

Read excerpt


# Control UI

Verify UI behavior at the real browser or Electron boundary. Reuse the
project's Playwright, Cypress, browser, or Electron harness before creating a
probe. Keep the data local and disposable.

## Workflow

1. Read the project's documented start command and identify the local URL or
   debug port.
2. Discover existing browser tests and stable app markers.
3. Select the target page by a positive root marker, role, label, or stable
   `data-*` attribute, not tab order or coordinates.
4. Capture the initial DOM/accessibility snapshot, screenshot, console state,