// 使用本项目的 CMake 工作流构建 xTools 或指定的 X_APP 目标。当用户要求编译、重新构建或生成打包产物时使用此技能。
| name | build-xtools |
| description | 使用本项目的 CMake 工作流构建 xTools 或指定的 X_APP 目标。当用户要求编译、重新构建或生成打包产物时使用此技能。 |
| argument-hint | [目标] [Qt路径] |
| disable-model-invocation | true |
当任务是编译此仓库、代码修改后重新构建或生成打包产物时，使用此技能。
X_APP 目标。CMAKE_PREFIX_PATH 指定 Qt MSVC 套件路径。C:/Qt/、D:/Qt/Qt/、D:/512/Qt/Qt/）搜索 Qt 版本。Tools/CMake/bin 或 Tools/CMake 子目录中。xTools。xTools_zip。参考命令：
call "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat" x64
cmake -S . -B build\my-build -G Ninja -DCMAKE_PREFIX_PATH=D:/Qt/Qt/6.10.3/msvc2022_64 -DCMAKE_BUILD_TYPE=Release
cmake --build build\my-build --target xTools
cmake --build build\my-build --target xTools_zip
若用户要求构建特定 xApp，在配置时添加 -DX_APP=<名称>，例如：-DX_APP=xOscilloscope。
示例：
cmake -S . -B build\xoscilloscope -G Ninja -DCMAKE_PREFIX_PATH=D:/Qt/Qt/6.10.3/msvc2022_64 -DCMAKE_BUILD_TYPE=Release -DX_APP=xOscilloscope
cmake --build build\xoscilloscope --target xOscilloscope
参考命令：
cmake -S . -B build/linux -G Ninja -DCMAKE_PREFIX_PATH=/path/to/Qt/6.10.3/gcc_64 -DCMAKE_BUILD_TYPE=Release
cmake --build build/linux --target xTools
Linux 打包目标（环境支持时）：xTools_deb、xTools_appimage。
build/ 下已存在构建目录，不能直接复用，需先确认 Qt 版本和生成器是否匹配。xProtocol是一个自定义协议序列化/反序列化工具，用户可以编辑自己的协议格式，可以控制消息的发送，可以解析接收到的消息。支持json格式的消息和二进制格式的消息体（负载）。用户要求修改协议定义、编辑消息内容、发送消息或解析接收消息时使用此技能。
Generates standalone Markdown reference documentation for any Qt/C++ source files — Qt Widgets classes, Qt Quick backends, Qt/C++ modules, plain C++ utilities, structs, free-function headers, and entry points like main.cpp. Use this skill to document any .h or .cpp file: Qt classes, plain C++ code, utility helpers, or application startup files. Triggers on: "document this class", "write docs for my C++", "document main.cpp", "C++ API docs", "document my Qt app", or whenever C++ or header files are provided and documentation is needed. Works with single files, pasted code, or entire project folders. DO NOT use if the user asks for QDoc format output.
Invoke when the user asks to review, check, audit, or look over Qt6 C++ code — or suggest before committing. Runs deterministic linting (60+ rules) then six parallel deep- analysis agents covering model contracts, ownership, threading, API correctness, error handling, and performance. Reports only high-confidence issues (>80/100) with structured mitigations. Read-only — never modifies code.
Generates standalone Markdown reference documentation for QML components and applications. Use this skill whenever you want to document QML files, create API reference docs for a QML component or module, document a Qt Quick application, or produce developer-facing documentation from .qml source code. Triggers on: "document this QML", "write docs for my QML", "create reference docs", "document QML component", "QML API docs", "document my Qt Quick component", "document my Qt app", or any time one or more .qml files are provided and documentation is needed. Works with single files, pasted code, or entire project folders. DO NOT use if the user asks for QDoc format output.
Invoke when the user asks to review, check, audit, or look over Qt6 QML code -- or suggest before committing. Runs deterministic linting (47+ rules) then six parallel deep- analysis agents covering bindings, layout, loaders, delegates, states, and performance. Optionally invokes system qmllint for type-level checks. Reports only high-confidence issues (>80/100) with structured mitigations. Read-only -- never modifies code.
Applies QML best practices when producing or working with QML source code. Use whenever QML code is the primary subject: writing, reviewing, fixing, refactoring, optimizing, or debugging QML files, components, or bindings. Do NOT trigger for purely conversational QML questions where no code is produced or examined (e.g. "explain how anchors work").