Control Ui

Community

AnastasiyaW

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.

Overview

Publisher	AnastasiyaW
Repository	`codex-claude-code-config`
Skill name	`control-ui`
Stars	212
Forks	32
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by AnastasiyaW on GitHub. Read the source before you install it.

Installation

Install the Control Ui AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/development/control-ui
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/development/control-ui

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git /tmp/codex-claude-code-config
mkdir -p .claude/skills
cp -r /tmp/codex-claude-code-config/skills/development/control-ui .claude/skills/control-ui

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Control Ui in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Control Ui on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Control Ui is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Read the project's documented start command and identify the local URL or debug port.
Discover existing browser tests and stable app markers.
Select the target page by a positive root marker, role, label, or stable data-* attribute, not tab order or coordinates.
Capture the initial DOM/accessibility snapshot, screenshot, console state, or network baseline relevant to the claim.
Perform one structural action: click, type, keypress, drag, scroll, navigate, or resize.
Capture the new state and assert the expected change.
Clean up the dev server, debug session, temporary profile, and artifacts.

Use verify-this for before/after claims. Use raw CDP only when higher-level APIs cannot provide the required CPU, heap, trace, network, or rendering signal. Do not install Playwright just for a one-off probe when an existing browser tool or dependency is available.

Evidence and privacy

Screenshots, traces, network bodies, and heap snapshots may contain private code or user data. Keep them outside public Git unless they are explicitly sanitized and approved. A public report should contain the command, revision, safe metric, and artifact hash or private location, not the payload.

Gotchas

A screenshot without an assertion proves that rendering occurred, not that the workflow is correct.
Coordinates and stale locators are fragile after navigation or layout change; select from the latest structure.
A successful page load does not prove console, network, accessibility, or keyboard behavior.
A visual diff can be caused by viewport, font, locale, or reduced-motion differences; record those inputs before interpreting it.

Troubleshooting

Symptom	Likely cause	Action
Wrong tab or window	Selector relied on tab order	Enumerate pages and choose a positive app marker
Click changes nothing	Stale locator or wrong state	Capture a fresh snapshot and wait for the state marker
Screenshot differs only on one machine	Fonts, viewport, scale, or locale drift	Pin the test inputs and classify as `INCONCLUSIVE` until comparable
Browser remains after the run	Cleanup path missed an exception	Use a bounded cleanup step and verify the process/profile is gone

Source

Adapted from Cursor Team Kit's MIT-licensed control-ui workflow: https://github.com/cursor/plugins/tree/main/cursor-team-kit/skills/control-ui

Frequently asked questions

What does the Control Ui AI skill do?

Why use Control Ui on TypingMind?

Because you install it once and use it with any model. Control Ui is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Control Ui in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/development/control-ui. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Control Ui?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Control Ui?

As many as you like. As long as a model supports skills, you can use Control Ui with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Control Ui AI skill free?

Yes. It is published on GitHub by AnastasiyaW under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Control Ui E2e

openclaw

OrganizationPopular

Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows,…

Discord E2e

Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and…

Openclaw Qa Testing

Run, watch, debug, extend, or explain OpenClaw qa-lab and qa-channel scenarios, artifacts, and live lanes.

Proof Video

Add subtitles, captions, narration cues, or zoom to a proof video or PR recording using repo-local capture helpers and a system ffmpeg renderer.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Control UI

Workflow

Evidence and privacy

Gotchas

Troubleshooting

Source

Frequently asked questions

Related AI Skills

Set up your own AI workspace now