novnc-webapp-control

Installation
SKILL.md

noVNC Webapp Control

Operate the real webapp in an isolated, observable browser. Treat the webapp as the product under test: enter requests through visible controls, observe its own progress UI, and fix the app or controller when the workflow cannot finish.

Control Contract

  • Allocate a dedicated X display, VNC port, noVNC port, CDP port, app port, and Chrome profile. Never reuse an unrelated automation profile.
  • Bind VNC, noVNC, CDP, and local app services to 127.0.0.1 unless the user explicitly asks for remote exposure.
  • Manipulate the webapp through Playwright/CDP locators and visible controls. Do not replace a failed UI interaction with a direct application API mutation.
  • Health probes may check service startup. They are not substitutes for browser actions.
  • Reuse one app tab and bring it to the front before every operation.
  • Keep one interactive noVNC client per desktop. Use x11vnc -nevershared -forever; do not leave legacy vnc_lite.html clients connected.
  • Add stable data-testid and state attributes to first-party UI when selectors are ambiguous.
  • Capture before, after, and failure screenshots plus a machine-readable status summary.
  • Require a visible confirmation for paid, destructive, publishing, or irreversible actions. Submit exactly once.
  • Scope generated-artifact discovery to the current job or result container. Never accept unrelated media merely because it appears elsewhere on the page.
  • Validate downloaded artifacts against the request using available evidence such as duration, dimensions, filename, hash, and visible result identity before copying or reporting success.
  • When a first-party app delegates to a second browser service, require the app to establish and report that service's observable noVNC desktop before delegation. A reachable CDP endpoint alone is not visible-operation proof.
Installs
1
GitHub Stars
1
First Seen
Oct 19, 2026