mcp-server-uiautomation
Copilot instructions4 starsChanged 8 months agoMITView on GitHub
UIAutomationMcp is a Windows-only automation toolkit for inspecting live desktop UI with Windows UI Automation. The active product surfaces are: - src\UIAutomationMcp.CLI (uiamcp) - src\UIAutomationMcp.McpServer - vscode-extension When changing code, start with: - docs\UIAUTOMATION-COM-REFERENCE.md - README.md - FEATURES.md
We split this copilot-instructions.md into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
When changing code, start with:
- Distinctive: line 21
Do not reintroduce legacy pre-migration naming.
- Distinctive: line 22
Keep CLI and MCP behavior aligned when you add or change UIA operations.
- Distinctive: line 24
Prefer focused docs and examples that match the current UIA-only repo.
≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
GitHub Copilot Instructions - UIAutomationMcp
Project focus
UIAutomationMcp is a Windows-only automation toolkit for inspecting live desktop UI with Windows UI Automation.
The active product surfaces are:
src\UIAutomationMcp.CLI(uiamcp)src\UIAutomationMcp.McpServervscode-extension
Read first
When changing code, start with:
docs\UIAUTOMATION-COM-REFERENCE.mdREADME.mdFEATURES.md
Core rules
- Do not reintroduce legacy pre-migration naming.
- Keep CLI and MCP behavior aligned when you add or change UIA operations.
- UI Automation access must remain safe for Windows COM/STA execution.
- Prefer focused docs and examples that match the current UIA-only repo.
- Validate changes with the smallest relevant build or smoke command before finishing.
Quick validation
dotnet build UIAutomationMcp.sln
dotnet run --project src\UIAutomationMcp.Smoke\UIAutomationMcp.Smoke.csproj
dotnet run --project src\UIAutomationMcp.CLI\UIAutomationMcp.CLI.csproj -- desktopCurrent architecture
UIAutomationMcp.ComInterop- typed bootstrap and UI Automation COM accessUIAutomationMcp.Service- shared query surface used by all entry pointsUIAutomationMcp.CLI- JSON-friendly terminal entry pointUIAutomationMcp.McpServer- MCP tool host for assistantsvscode-extension- packaged VS Code surface bundling the CLI and MCP server
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository3 other files it gives its agents.
- .github/agents/copilot-instructions.mdCopilot instructions
- uia-cliSkill
- uia-mcpSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.