菜单
The exact incantations to build and run this repo's test suites headlessly — UE's CLI is arcane and these commands are load-bearing, in this order. Use whenever building or running ReactiveUI.* automation suites, benches, or the markup drift gate.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
The runbook for supporting a NEW Unreal Engine version (5.7, 5.8, …) — run the header-diff automation, classify what changed in Slate/UMG, and walk the implementation checklist (widgets, schema, docs version manifest, CI matrix, per-engine packaging). Ported from the Unity sibling's add-unity-version process. Use whenever Epic releases an engine version the plugin should support.
The house development methodology for ReactiveUI-Unreal — the research→develop→test→bughunt→fix→commit loop, the UE gate ladder (compile → suites → boot check → demo), branch/PR model, changelog/version tables, and the laws that never bend. Use for any code change in this repo.
How the .uetkx grammar stays byte-compatible with the family (.uitkx Unity — the origin; .guitkx Godot) and how the two in-repo implementations (C++ compiler, TS language server) stay in lockstep — corpus cases, goldens, the .pending divergence protocol, and cross-repo sync. Use for ANY lexer/parser/formatter change, and at release time for the sibling drift check.
Author a .uetkx component for ReactiveUI-Unreal — file placement, declaration kinds and companion-file layout, props/hooks/events/directives/styling syntax, what the compiler generates, and the done-checklist. Use when writing or reviewing .uetkx markup. (Toolchain lands in Phase 3 — until then this is the authoring contract.)
The ReactiveUI-Unreal release runbook — draining the pending changelog, version bumps, the two-lane changelog system, packaging per engine version, the merge→fast-forward→Publish flow, and the manual Fab checklist with its compliance items. Use when preparing, staging, or publishing a release of any artifact.
Rebuild the VS Code and/or VS2022 .uetkx extensions locally for F5 / Extension-Development-Host testing. Use when the user says "rebuild for F5", "test the extension", "build the language server locally", or after editing ide-extensions/lsp-server/**, ide-extensions/vscode-uetkx/**, or the shared grammar/schema. Covers the npm pipelines, server bundling, artifact verification, and the VS2022 experimental-instance flow. Does NOT cover marketplace releases — publish.yml owns those.
| name | test-run |
| description | The exact incantations to build and run this repo's test suites headlessly — UE's CLI is arcane and these commands are load-bearing, in this order. Use whenever building or running ReactiveUI.* automation suites, benches, or the markup drift gate. |
Environment facts first (verify, don't assume): <Engine> =
C:\Program Files\Epic Games\UE_5.6 (the floor; UE_5.7 also installed + battery-verified
2026-07-14 — swap the path to run the ladder against it; MSVC 14.44 — UE warns
"not preferred (14.38)" but accepts). <abs> below = this repo's absolute path. ALWAYS
redirect engine output to a file — piping block-buffers and hides everything (family scar).
:: 0. Build (compile step — Development Editor)
<Engine>\Engine\Build\BatchFiles\Build.bat ReactiveUIUnrealDemoEditor Win64 Development -Project=<abs>\ReactiveUIUnrealDemo.uproject -WaitMutex
:: 1. Markup compile sweep + drift gate (Phase 3+; skip while no .uetkx exist)
<Engine>\UnrealEditor-Cmd.exe <abs>\ReactiveUIUnrealDemo.uproject -run=RUICompile -check
:: 2. Suites (headless, no GPU)
<Engine>\UnrealEditor-Cmd.exe <abs>\ReactiveUIUnrealDemo.uproject ^
-ExecCmds="Automation RunTests ReactiveUI; Quit" ^
-unattended -nopause -nosplash -nullrhi -log -stdout -FullStdOutLogOutput ^
-ReportExportPath=<scratch>\report > <scratch>\run.log 2>&1
<scratch>\report\index.json (succeeded/failed counts) — the
exit code alone is unreliable.Automation RunTests ReactiveUI.Core runs that suite;
ReactiveUI.Widgets.Button a single widget's tests. Suite map: Boot (module startup + root
mount — the gate ladder's boot check, NEVER optional), Core, Update, Style, Widgets.*,
Demos (mounts every demo — the real "generated code runs" check), Uetkx, Contract,
Hmr, Umg, Mvvm, CommonUI.ReactiveUI.Bench is NOT pass/fail — numbers go to plans/BENCH_BASELINES.md WITH the
machine/config context that file demands; cross-machine comparisons are invalid.node ide-extensions/scripts/changelog.mjs verify && node scripts/verify-mirror.mjs && node scripts/check-headers.mjs && node scripts/lint-skills.mjs && node scripts/docs-drift.mjs> run.log 2>&1 is not optional style, it's how you SEE failures.tests/guitkx_build.gd — suites consuming stale generated
code produce phantom passes/failures; compile first, always, in this order.