As with all of these tools, it's easy to create things from scratch. Claude can write a C# script that does everything here. The video gives the game away a bit by asking you to pass in "references", but ideally AI should be able to find those references for you.
For any sort of value proposition, I would need to see actual two-way information exchange between the editor and scripting: something that can understand and build off what's already there -- e.g. "add a button at the bottom-left [with the same look and feel as the other buttons]". (JetBrains' Rider already does this a little bit.) But that might be a bit too far for a wrapper app.
As with all of these tools, it's easy to create things from scratch. Claude can write a C# script that does everything here. The video gives the game away a bit by asking you to pass in "references", but ideally AI should be able to find those references for you.
For any sort of value proposition, I would need to see actual two-way information exchange between the editor and scripting: something that can understand and build off what's already there -- e.g. "add a button at the bottom-left [with the same look and feel as the other buttons]". (JetBrains' Rider already does this a little bit.) But that might be a bit too far for a wrapper app.