القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| 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"] |
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.
Run all commands from the repo root via:
dotnet run --project src/CcClick -- <command> [options]
| 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 |
--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 pathAll commands output JSON to stdout. Errors go to stderr as JSON with exit code 1.
| 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 | « |
| Tab | ControlType |
|---|---|
| Terminal | TabItem |
| Source Control | TabItem |
| 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 |
Right-clicking a session tab opens a context menu with these MenuItems:
Clicking + New Session opens a modal dialog. It shows:
The dialog is a modal child of CC Director (not a separate top-level window).
Parse the user's request from $ARGUMENTS to determine what UI action(s) to perform.
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.
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"
Take a screenshot after the action to show the result. Use the Read tool on the PNG to display it to the user.
Clean up screenshots from tmp_build_output/ when done if they're no longer needed.
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.--window) to capture them, and take the screenshot immediately after the right-click.sleep 0.5 between click and screenshot if the UI needs time to update.tmp_build_output/ to keep the repo clean (it's gitignored).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.Relocate a live session to another cc-director slot or Director - approval-gated handover through the GATEWAY, the seed identifies itself as a moved session, the TARGET keeps the source's original name, the source is renamed "[MOVED]" and put on hold so the user can close it. Triggers on "/move-session", "move session", "migrate session", "transfer session".
INTERNAL reference, NOT shipped with the installer. The in-repo expert on every coding-agent CLI CC Director can run (Claude Code, Codex, Gemini, OpenCode, Grok, Copilot, Cursor, Pi). Knows each agent's command line, config files, context-injection points, lifecycle hooks and events, SDK/API/server mode, transcript format, session semantics, and how CC Director drives it. Triggers on "agent-expert", "agent expert", "how does <agent> inject context", "<agent> hooks", "<agent> events", "<agent> CLI reference", "which agents support X", "agent capability matrix".
How a mission is RUN in this repository - the Architect, the Manager, the Workers, and the independent Inspector, plus the four standing laws (ask up front then run alone, and NEVER guess - bring the owner in when something is genuinely undecidable; the mission branch holds the work and only the Architect lands it on main; a different agent family inspects before anything reaches main; merged to origin/main is the only done). Read this BEFORE starting or seeding any mission, and before writing any mission brief. Triggers on "/mission", "start a mission", "run a mission", "seed an architect", "write a mission brief", "mission brief", "who merges", "mission roles".
DevThrottle - "Mission Control for Claude Code". A desktop app (binary cc-director.exe) that runs and supervises multiple Claude Code sessions and ships cc-* CLI tools on PATH. Agents drive the fleet through the cc-devthrottle command, not by calling the Director over HTTP. Triggers on "/dev-throttle", "/devthrottle", "/cc-director", "what cc tools", "list tools", "available tools", "devthrottle api", "session manager", "mission control".
Talk to other DevThrottle sessions across the fleet. Use when you want to list running sessions, rename this session, message another session, ask another session a question and get its answer, or open a new session - from inside a session. Triggers on "/fleet-comms", "message another session", "talk to another session", "ask another session", "rename this session", "rename session", "list sessions", "what sessions are running", "open a session", "spawn a session", "cc-devthrottle", "fleet messaging", "session intercommunication".
Guided run-book for cutting a DevThrottle release - assemble the changes, write the release notes, coordinate the internal docs site, cut the tag, and announce it. Triggers on "/release-manager", "cut a release", "prepare a release", "ship a release", "do the release".