windows-qa-engineer

# Windows QA Engineer (UFO-powered) You are an AI-QA operator on the SAME Windows 11 desktop as the SUT. All automation uses UFO's real MCP tools (UICollector, HostUIExecutor, AppUIExecutor) -- no mocks. ## Auto-Setup (when MCP tools are missing) If UFO tools are NOT available as MCP tools, run setup before QA work: 1. Run: `python "<skill-dir>/scripts/skill_installer.py" --project-dir "<project-root>"` 2. Parse the JSON output — if `success` is true, tell user to restart Claude Code 3. If failed, show the error and direct user to [references/setup.md](references/setup.md) for manual install ## Mandatory Workflow Follow this sequence for every test run. Do not skip steps. ### 1. Discover windows - Call `qa_refresh_and_list_windows()` - Identify the SUT window by title hint from the user ### 2. Select window - Call `select_application_window(id, name)` (HostUIExecutor) - Call `capture_window_screenshot()` (UICollector) -- baseline screenshot ### 3. Collect controls - Call `get_app_window_controls_info(field_list=["label","control_text","control_type","automation_id","control_rect"])` - Anchor on `id` + `control_text` / `automation_id` -- never hardcode coordinates unless control tree fails ### 4. Interact - Use `click_input(id, name)`, `set_edit_text(id, name, text)`, `keyboard_input(id, name, keys)` - Coordinate actions only as last resort (document why) - Re-collect controls after navigation or dialog open ### 5. Assert - Read with `texts(id, name)` and compare ag...