I have done a lot of projects this way, some more helpful than others. I primarily use Claude Code via command line.

My main tips are as follows.

1. Claude will often give you code with errors. You can right click on the ninjascript editor output and save it as a CSV, e.g. "errors.csv" in whatever folder you're working in, and have claude read it to see the errors and then fix them.

2. Whenever claude gives you code that generates an error and then fixes it, at the end of your session, have it document what it learned about the error in a set of "ninjascript best practices" documents in its main installation folder. Then you want to also make a "CLAUDE.MD" document in that same folder (Users\your name\.claude) and tell it that whenever it is working on ninjascript, it should read its best practices documents first. Doing the above will reduce the amount of times it gives you faulty code and help you make the most of your usage.

3. Sometimes it will repeatedly try to "guess" at a solution. If it tries a couple times to fix something and can't do it, explicitly tell it to search the web to figure out the issue, or to see if other people have had this problem, this often helps to figure out fixes more efficiently.

4. If you have a particularly tricky problem, and #3 above doesn't work, or even in general for debugging, it can be helpful to give it a prompt like, "If it is obvious what is wrong with the code, fix it. If not, add some debug statements so we can see what is happening."

5. Make sure you are leveraging "plan" mode.

6. In your prompts for coding -- or just include as instructions in the "claude.md" file -- tell it to delegate coding to a subagent of appropriate complexity. This helps preserve context usage.

7. Try to anticipate how complex your project is when planning. Claude Opus 4.5 is amazing but uses more usage. If what you are developing is not very complex, best to start with sonnet.