What they did
The poster, who does not code and holds three jobs, had paid a studio about $50k to build her first game. For the second she worked alone with Claude Code on Opus 5.5 connected to Unity 6 through a Unity MCP, starting from a plain design doc and a CLAUDE.md. Claude Code wrote nearly all the C#. When OBS lagged on her laptop it built an in-engine replay recorder, later a scripted version that turns a shot list into a finished clip. With no playtesters, it built a local API into the built game; she wrote eight player profiles, and eight agents each played the full 60-day demo and filled in an evaluation sheet. It also added 14 languages with a test for text overflowing buttons at three screen sizes, and about 360 automated tests. Music, voice-over from her own voice and 3D renders came from Higgsfield.
How it went
In a few weeks she had a playable game with a live Steam page, for under $700, with a demo due on 2 December. Comparing the eight persona sheets turned up a soft-lock, a bug that fired for the wrong reason in 7 of 8 runs, and an economy exploit before any human played it. The play, find, describe, fix loop ran about 300 times. She kept every design and balance decision. She later fed the studio-built first game's source to Claude, which fixed some open bugs there.
Worth knowing
She calls the hour spent on the design doc and CLAUDE.md before the first prompt the most valuable of the project. The persona playtest needs a way for agents to drive the built game, which Claude Code had to build first. A commenter noted that this much regression testing is standard practice for professional developers. Sales so far are small; she joked about two.