Skip to content
Skills Library
Programming · Testing

ui-test

/ui-test

Interact with and test the CC Director WPF app using the cc-click CLI tool. Use this to click buttons, read text, take screenshots, list elements, right-click session tabs, and navigate the UI.

Repository
devthrottle ↗
Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Interact with and test the CC Director WPF app using the cc-click CLI tool. Use this to click buttons, read text, take screenshots, list elements, right-click session tabs, and navigate the UI.

Arguments

/ui-test [action or test description]
Original author description

Interact with and test the CC Director WPF app using the cc-click CLI tool. Use this to click buttons, read text, take screenshots, list elements, right-click session tabs, and navigate the UI.

How it works

  1. Input: $ARGUMENTS
  2. The cc-click CLI Tool
  3. CC Director UI Map
  4. Instructions
  5. Tips
Original SKILL.md headings · 191 lines, 1,062 words
SKILL.md preview
---
name: ui-test
description: Interact with and test the CC Director WPF app using the cc-click CLI tool. Use this to click buttons, read text, take screenshots, list elements, right-click session tabs, and navigate the UI.
disable-model-invocation: true
argument-hint: [action or test description]
---

# CC Director UI Automation

Interact with the CC Director WPF application using the `cc-click` CLI tool (located at `src/CcClick`). Use this skill to test UI interactions, take screenshots, and verify app behavior.

## Input: $ARGUMENTS

## The cc-click CLI Tool

Run all commands from the repo root via:
```
dotnet run --project src/CcClick -- <command> [options]
```

### Available Commands

| Command | Description |
|---------|-------------|
| `list-windows` | List visible top-level windows |
| `list-elements` | List UI elements in a window |
| `click` | Click (or right-click) a UI element |
| `type` | Type text into a UI element |
| `screenshot` | Capture a screenshot |
| `read-text` | Read text content of a UI element |

### Common Options

- `--window "CC Director"` / `-w` — Target the CC Director window
- `--name "Button Text"` — Find element by display text
- `--id "AutomationId"` — Find element by AutomationId
- `--type Button` / `-t` — Filter by ControlType (Button, TextBox, ListItem, TabItem, MenuItem, Text, Edit, etc.)
- `--depth N` / `-d` — Max tree traversal depth (default 25)
- `--right` / `-r` — Right-click instead of left-click
- `--xy "x,y"` — Click at absolute screen coordinates
- `--output path.png` / `-o` — Screenshot output path

### Output

All commands output **JSON to stdout**. Errors go to **stderr as JSON** with exit code 1.

## CC Director UI Map

### Main Window Buttons (by AutomationId)

| Button | AutomationId | Name |
|--------|-------------|------|
| New Session | `BtnNewSession` | `+ New Session` |
| Kill Session | `BtnKillSession` | `Kill Session` |
| Reconnect | `BtnReconnect` | `Reconnect` |
| Open Logs | `BtnOpenLogs` | `Open Logs` |
| Send (prompt) | — | `Send` |
| Refresh | — | `↻` |
| Pipe Toggle | `PipeToggleButton` | `«` |

### Tabs (by Name)

| Tab | ControlType |
|-----|-------------|
| Terminal | TabItem |
| Source Control | TabItem |

### Other Key Elements

| Element | AutomationId | ControlType | Notes |
|---------|-------------|-------------|-------|
| Session list | `SessionList` | List | Contains session ListItems |
| Session tab | — | ListItem | Name is `CcDirector.Wpf.SessionViewModel`; children have session name + status as Text elements |
| Prompt input | `PromptInput` | Edit | Text input at bottom of window |
| Tab container | `SessionTabs` | Tab | Contains Terminal and Source Control tabs |

### Session Tab Context Menu (right-click a ListItem)

Right-clicking a session tab opens a context menu with these MenuItems:
- **Rename** — Rename the session
- **Open in Explorer** — Open working directory in Explorer
- **Open in VS Code** — Open working directory in VS Code
- **Close Session** — Close/remove the session

### New Session Dialog

Clicking `+ New Session` opens a modal dialog. It shows:
- Recent sessions list
- Repository list to select from
- Browse button for custom path
- Create / Cancel buttons

The dialog is a **modal child** of CC Director (not a separate top-level window).

## Instructions

1. **Parse the user's request** from `$ARGUMENTS` to determine what UI action(s) to perform.

2. **Ensure CC Director is running:**
   ```
   dotnet run --project src/CcClick -- list-windows --filter "CC Director"
   ```
   If not found, tell the user to launch it first.

3. **Perform the requested action(s).** Common patterns:

   **Click a button:**
   ```
   dotnet run --project src/CcClick -- click --window "CC Director" --id "BtnNewSession"
   ```

   **Right-click a session tab** (use coordinates from list-elements):
   ```
   dotnet run --project src/CcClick -- list-elements --window "CC Director" --type ListItem
   # Then right-click using the center of the bounding rect:
   dotnet run --project src/CcClick -- click --xy "130,80" --right
   ```

   **Click a context menu item** (after right-clicking):
   ```
   dotnet run --project src/CcClick -- click --window "CC Director" --name "Rename"
   ```

   **Type into the prompt input:**
   ```
   dotnet run --project src/CcClick -- type --window "CC Director" --id "PromptInput" --text "hello world"
   ```

   **Switch tabs:**
   ```
   dotnet run --project src/CcClick -- click --window "CC Director" --name "Source Control"
   ```

   **Read element text:**
   ```
   dotnet run --project src/CcClick -- read-text --window "CC Director" --name "SESSIONS"
   ```

   **Take a screenshot:**
   ```
   dotnet run --project src/CcClick -- screenshot --window "CC Director" --output tmp_build_output/shot.png
   ```
   For context menus or popups, use a **fullscreen** screenshot (omit `--window`):
   ```
   dotnet run --project src/CcClick -- screenshot --output tmp_build_output/shot.png
   ```

   **Discover elements dynamically:**
   ```
   dotnet run --project src/CcClick -- list-elements --window "CC Director" --type Button
   dotnet run --project src/CcClick -- list-elements --window "CC Director" --depth 4
   ```

   **Close CC Director gracefully** (click the window Close button):
   ```
   dotnet run --project src/CcClick -- click --window "CC Director" --id "Close"
   ```
   Verify it's gone:
   ```
   dotnet run --project src/CcClick -- list-windows --filter "CC Director"
   ```

   **Build and start CC Director:**
   ```
   dotnet build src/CcDirector.Wpf -c Debug
   cmd.exe //c start "" "src\CcDirector.Wpf\bin\Debug\net10.0-windows\win-x64\cc-director.exe"
   ```
   Wait for startup then verify:
   ```
   sleep 2
   dotnet run --project src/CcClick -- list-windows --filter "CC Director"
   ```

   **Full restart cycle** (close, build, launch, verify):
   ```
   dotnet run --project src/CcClick -- click --window "CC Director" --id "Close"
   sleep 1
   dotnet build src/CcDirector.Wpf -c Debug
   cmd.exe //c start "" "src\CcDirector.Wpf\bin\Debug\net10.0-windows\win-x64\cc-director.exe"
   sleep 2
   dotnet run --project src/CcClick -- list-windows --filter "CC Director"
   ```

4. **Take a screenshot** after the action to show the result. Use the Read tool on the PNG to display it to the user.

5. **Clean up** screenshots from `tmp_build_output/` when done if they're no longer needed.

## Tips

- Session ListItems all share the same name (`CcDirector.Wpf.SessionViewModel`). To target a specific session, use `list-elements --type ListItem` to get bounding rects, then `click --xy "x,y"` with the center of the desired item.
- Context menus disappear when the window loses focus. Use fullscreen screenshots (no `--window`) to capture them, and take the screenshot immediately after the right-click.
- The New Session dialog is modal. After opening it, elements can be found within the CC Director window tree.
- Add `sleep 0.5` between click and screenshot if the UI needs time to update.
- All screenshot paths should use `tmp_build_output/` to keep the repo clean (it's gitignored).
- **NEVER use `taskkill` to stop CC Director** — it kills the process ungracefully and orphans the embedded console windows. Always use the Close button: `click --window "CC Director" --id "Close"`. This lets the app shut down cleanly.
- After restarting CC Director, use "Reconnect" to re-adopt any running Claude sessions.

Versions

RepositoryScoreLicence
This page · thefrederiksen/devthrottle100MIT
zly2006/zhihu-plus-plus100AGPL-3.0
mostafa-drz/claude-skills100MIT
browserbase/skills95MIT
zanderadam/engy90MIT

Database snapshot: 13.11.2026 · package version 62db017c8408 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100agent-browser
    Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a…
  • 93winapp-ui-automation
    Inspect, drive, and verify a running Windows app UI via winapp ui (UI Automation): find elements, click, type, read text/values, wait for state, take screenshots in WinUI, WPF, WinForms, Win32, or Electron apps. Use to check, test, or act on a live app; for WinUI XAML internals, use winui-devtools.
  • 100playwright-cli
    Automate browser interactions, test web pages and work with Playwright tests using the playwright-cli command. Use when the user wants to open a browser, navigate pages, click elements, fill forms, take screenshots, run Playwright tests, debug browser automation, or perform any…
  • 100browser
    Browser automation with persistent page state. Use when the assistant needs to inspect, automate, or interact with a page: click, fill, login, scrape, extract data, test UI, take screenshots, or report what is visible. Do not use this skill for plain link opening; use `open…
  • 100agent-browser
    Browser automation via agent-browser CLI. Use when the user needs to navigate websites, fill forms, click buttons, take screenshots, extract data, or test web apps.
  • 95browser
    Automate web browser interactions using natural language via CLI commands. Use when the user asks to browse websites, navigate web pages, extract data from websites, take screenshots, fill forms, click buttons, or interact with web applications.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.