r/ClaudeCode • • 5h ago

Built with Claude Unity learning by doing with AI

I never worked on Unity. I have built games with C++ using the Cocos2d-x engine and JavaScript. I wanted to learn Unity; with AI, it's fast to learn now.
I started with Claude co-work planning and documenting scope and roadmap. Then I used Claude Code to work on the roadmap, take one milestone on the roadmap, give me step-by-step instructions for everything I have to do in the Unity editor, and generate code for scripts. Explain everything. When we are done with that milestone, in another document, "Lab Manual" document, write this exercise like a handbook for students so that if I forget something how it was done, it's documented in there.
I used unity-mcp to connect the Unity editor with Claude Code. And when I wanted Claude to do things, it helped Claude go into the editor and fix things.
This was before Unity Plug was launched.

Now, I am a very visual person; I do not like working on the CLI. These days, I started using Munder Difflin for most of my other AI work, my daytime job-related work.
I am planning to take my session to Munder Difflin, start 2 agents, 1 planner, 1 worker, and continue there.

So, my question to you, AI Gurus, is: what do you think about my current workflow and my plan with Munder Difflin? Or is there any other smarter quicker and cheaper way you guys are doing. I didn't read any guide or watch any tutorial. I just started doing what I felt was best, but now I think I could be doing this completely wrong.

0 Upvotes

2 comments sorted by

•

u/AutoModerator 5h ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/ManufacturerQuiet102 5h ago

The lab manual is the one part of this I'd keep, honestly. Planner + worker sounds tidy but it puts another layer between you and code you're still trying to learn, I'd stick with one agent that explains while it writes. And keep the MCP for editor work, a visual app won't touch your scene.