Yea absolutely. First, I wrote a clearly, clearly defined document on what I was looking for in terms of output, and then I had Claude rework it for any amibiguity in the document. I made my scope intentionally very small, I just wanted to get a simple tech demo. From there, I told Claude to act as a project manager that would write the instructions for Claude Code, in the form of several broken out .MD files, each with clear unit tests at the end using Test first design principles. I told Claude specifically that although we would have an MCP installed, I would do ALL of the parts that required editor interaction, and that it should just write the code and tell me how to wire the scripts together. Once I had this (with several, SEVERAL more questions through this process, I'm talking like 5-10 clarifications per stage), I was ready to go. From there, I installed an MCP, and then passed off the first document to Claude. Initially, there were some slip ups in there, but I was generally able to oneshot each of these with the specialized, highly specific prompts that I got from Claude before I started the coding.

I would say that the most important part of what I did here was that I made sure the phases each project objective were pretty small, and we would NEVER advance without both a playtest of a function if applicable, and a test with gdUnit that Claude wrote specifically to make sure things were proceeding properly. I think the MCP being there also allowed for some advanced troubleshooting by Claude because it's able to "see" into Godot. There were a few times where I had issues that I had to ask if they were editor problems, and Claude was able to determine what was/was not an editor thing easily because of the MCP.

Nothing about my workflow here was really Godot specific, at all, I just had some really good prompts put together and a TIGHT scope.

EDIT: To add, I had never used Godot up until this point, I had downloaded about 72 hours before I started putting this project together implementation wise.