Drives a running Blender (via the blender MCP server) to create a custom NovaLogic object model — built procedurally or from a generator — names every object and material to ONED's convention so the round trip is lossless, then exports it to ASE with the bundled opennova add-on. Use when asked to create, author, or model a custom object / 3di in Blender, generate a game model, or export Blender geometry to .ase.
Launches this repo's Godot project — the ONED editor or the game runtime — with the native extension and game assets correctly set up, and watches its output. Use when asked to run, launch, demo, screenshot, or visually verify the editor/runtime, when the generic run/verify skills need this project's launch procedure, or when the editor seems to be running stale native code.
Ask which skill or flow fits your situation. A router over the skills in this repo.
Implement a piece of work based on a PRD or set of issues.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Scaffolds a new NovaLogic format library under libs/ end to end — CMake target, opennova namespace, parser/writer, fixtures with LFS and asset-gating policy, roundtrip ctest, and optional GDExtension binding. Use when adding support for a new game file format, or when extracting a subsystem into a new portable library.
Grilling session that challenges a reimplemented system against the original binary witnessed in IDA Pro via the ida-pro-mcp server. Finds the reimpl code and the corresponding original functions, decompiles the originals, and interrogates every behavioral divergence — constants, struct layout, control flow, fixed-point scaling, edge cases — updating IDA, the source, and the tracked RE record inline, ending in a per-system verdict landed via the re-doc skill. Use when verifying a reimplemented system matches the original, when re-verifying after a divergence fix, or when a TODO says something needs an IDA grill. For a new question about the original engine with no reimpl to verify, use engine-research instead.