skills.rest
cursor
cursorOFFICIAL
Explore all skills by this author →
WebsiteGitHub

control-ui

Build or adapt local browser harnesses to verify UI behavior.

2.6k|204|Updated Jan 23, 2026
Search Tags:#automation#accessibility#playwright#cdp#ui-testing#visual-diff#browser-harness
One-click install
npx skills add https://github.com/cursor/plugins --skill control-ui
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: control-ui
Source: https://github.com/cursor/plugins/tree/main/cursor-team-kit/skills/control-ui
Command: npx skills add https://github.com/cursor/plugins --skill control-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use local browser automation to verify UI behavior with evidence. First reuse the repo's own Playwright, browser, or Electron harness if it exists; otherwise assemble a temporary local harness around the app's dev server or Chromium debug port.

Core Features & Use Cases

  • Reuse existing harnesses from the repository and adapt to new UIs for faster validation.
  • Support both web apps and Electron/Chromium-based UIs with optional remote debugging ports.
  • Capture artifacts like screenshots, console logs, network logs, CPU profiles, traces, or heap snapshots to document results.
  • Provide guardrails and best practices for stable element selectors and accessibility checks.

Quick Start

Start the app locally and run a minimal Playwright probe to verify UI behavior and capture a baseline screenshot.

Frequently Asked Questions about control-ui

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

FAQPage Schema
How do I verify UI behavior using local browser automation?▼

Verify UI behavior with local browser automation by running a Playwright probe against your dev server to capture screenshots, console logs, and inspect runtime state for evidence-based validation.

Can I run Playwright tests against an Electron app using a remote debug port?▼

Playwright tests can target Electron apps by connecting to a Chromium remote-debug port, enabling UI verification tasks like screenshot capture and accessibility checks within your existing harness.

What's the best way to capture visual diffs and CPU profiles during UI testing?▼

Capture visual diffs and CPU profiles during UI testing by adapting a local CDP harness to collect artifacts like screenshots, traces, and heap snapshots that document application performance and visual state.

Do I need to set up a local dev server to inspect UI behavior?▼

Setting up a local dev server or Chromium remote-debug port is required to provide a stable target for page selection markers, element selectors, and safe disposable test data during UI verification.

Why should I reuse existing browser harnesses instead of creating a new one?▼

Reusing existing browser harnesses from your repository accelerates validation by adapting established configurations to new UIs, avoiding the overhead of assembling a temporary local harness from scratch.

How do I ensure stable element selectors for accessibility checks?▼

Ensure stable element selectors for accessibility checks by applying guardrails and best practices provided during harness setup, utilizing stable page selection markers to consistently target UI components.

Related Skills

Explore More Software Engineering Skills→
StudyDriftStudyDrift
58

control-ui

Builds and adapts a browser/CDP harness to inspect web, IDE, or Electron UI.

Official
Intermediate
CenredJunCenredJun

performance-profiling

Profile Node.js, browser, React, and database performance to rank bottlenecks.

Community
Advanced
cffrankcffrank

visual-qa

Capture Playwright-based screenshots across devices and create UI evidence reports.

Community
Intermediate
LambdaTestLambdaTest
350

selenium-skill

Generate Selenium WebDriver automation scripts in Java, Python, JavaScript, C#, Ruby, or PHP.

Official
Advanced