Repository navigation
2.0.1
🚀 2.0.1 - Editor tasks on all four engines
Planning and verifying editor-side changes is no longer Unity-only. Godot 4, Godot 4 .NET and Unreal Engine 5 now ship their own planning vocabulary and verification checks, alongside a stricter direct-edit safeguard that applies to every engine.
✨ Planning and verification vocabulary for Godot 4, Godot 4 .NET and Unreal Engine 5
/unikit-plan used to write Editor: steps for Unity only; the other three engines got none. Each engine now has its own vocabulary for what counts as an editor change, and /unikit-verify knows how to confirm it through that engine's MCP server.
What's included
Editor:tasks now resolve into Godot, Godot .NET and Unreal Engine 5 concepts - scenes, UI, VFX, animation, assets and project settings, the same six kinds Unity already uses- Editing a Blueprint graph in Unreal Engine 5 always counts as an editor change; it lives inside a binary asset with no text to review
/unikit-verifyconfirms each change by reading it back from the live editor, with engine-specific guidance (e.g. a stale read on Godot after a file is written outside the editor, or batching checks on Godot .NET to avoid repeated project rebuilds)- Each new engine's pitfalls guidance is a placeholder for now, pending validation on a real project - Unity's is already filled in
♻️ The direct editor-edit route fails closed
/unikit-implement now reads whether a direct text edit is safe from /unikit-plan's own installed rules, since it never shipped that check itself. When those rules are missing, every format is treated as unsafe and the task is handed back for manual editing instead of being edited blind.
- On Unreal Engine 5,
directis now offered only for settings files (Config/Default*.ini) - levels and assets are binary and can't be edited as text
🐛 Fixes
/unikit-verifyno longer treats a missing editor-check section as a dead end - it falls back to a general evidence rule instead of stalling- Unity's planning rules pointed at the wrong rules folder; the path is corrected
🛠 Internal Improvements
Technical changes
- Install tests now cover all four engines' planning templates, including the one engine where the docs and planning vocabularies diverge (Godot 4 .NET)
- New checks keep each engine's verification rules in sync with its planning rules
- Engine template files are checked project-wide for stray template variables that would otherwise leak to users as literal text
Full Changelog: 2.0.0...2.0.1