yanivkalfa

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.

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.

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.

The human-in-the-loop bug loop for the real Unreal editor — the AI prepares, fixes, verifies, and applies; the owner tests in a live UE editor; repeat until dead. Use for bugs only reproducible in-editor/PIE, and for packaged-fidelity verification.

Runbook for bringing the library up to a newly released Godot version — dump + diff ClassDB between the old and new binaries, classify every added/removed Control class/property/signal, apply the AUTOMATION.md checklist (bundled LSP dump, curated schema, docs versionManifest, CI + verified-on stamps), and verify the full matrix. Use when the user says a new Godot version is out or asks to support/verify one.

The house development methodology for ReactiveUI projects (Godot + Unity + analyzer) — research→develop→test→bughunt→fix→commit→repeat, production-grade only, plus the changelog and version-bump rules every change must follow.

Run the local field-test loop for the Godot native editor (reactive_ui + reactive_ui_editor + bundled analyzer) — the AI prepares, fixes, verifies, and applies; the user tests in a real Godot editor; repeat until the bug is dead.

Create a new .guitkx component for ReactiveUI-Godot — file placement, component/props/hooks/events syntax, children, styling, and what the compiler generates.

The ReactiveUI-Godot release runbook — version bumps, the two-lane changelog system (hand-written library lane vs script-generated tooling lane), Discord notes, verification gates, and the merge→fast-forward→Publish flow. Use when preparing, staging, or publishing a release of any artifact in this repo.

Add support for a new Unity version to ReactiveUIToolKit. Run when a new Unity release is available (user says "add Unity 6.5 support", "new Unity version came out", etc.). Discovers API changes via the automation~ diff scripts, classifies them, and implements support across all layers (PropsApplier/Style/StyleKeys/CssHelpers, schema, LSP, docs site) plus record-keeping.

The centralized IDE-extension changelog system. Use when adding a changelog entry, bumping extension versions, releasing, or editing any of ide-extensions~/changelog.json, scripts/changelog.mjs, the per-IDE CHANGELOG.md, vscode/README.md, or UitkxVsix/overview.md. Covers the add/extract/extract-overview/verify commands, the generated-marketplace-pages rule (edit templates, never outputs), and the Windows argv mojibake pitfalls.

Style and hard constraints for Plans~/DISCORD_CHANGELOG.md entries (the Discord release-notes posts). Use whenever adding or editing an entry there — hard 2000-char-per-entry cap, ASCII-only, prepend-only.

Rebuild the VS Code and/or Visual Studio 2022 extensions locally for F5 / Extension-Development-Host testing. Use when the user says "rebuild for F5", "rebuild the extension", "build the LSP server locally", "test the extension change" or after editing files under `ide-extensions~/language-lib/`, `ide-extensions~/lsp-server/`, `ide-extensions~/vscode/`, `ide-extensions~/visual-studio/`, or `Editor/HMR/`. Covers the full local pipeline — language-lib build, LSP server emit, TS client bundle, VSIX server-binary copy — and the artifact-size verification step. Does NOT cover Marketplace releases — those are handled by `.github/workflows/publish.yml`.