正在加载视频...
视频加载失败
A solo developer building an ocean ship game with Claude Opus 5.5 has shared his workflow and costs, alongside a free playable demo. → He runs a separate Claude session for each game system and talks only to a 'manager' session that messages the rest → A decisions.md file... show more
7 条评论

一个人用多个 Claude 会话造远洋船游戏 只跟一个 manager 会话说话 省的是上下文 贵的是那份 decisions.md 得自己盯 多会话编排的门槛从来不在工具 在记录

The manager-session architecture is the standout idea.

that decisions.md file is a genius way to avoid feature creep in long projects

A decisions.md file alongside separate system chats seems like a practical way to keep the project’s logic from drifting.

This is very close to how I’ve ended up working too. The part I’d add is aggressive verification - game agents can pass every automated check and still produce something visibly wrong. Separate workers + clear ownership work well, but for 3D/game work I’ve learned the rendered pixels still have to be the final judge.

a four-funnel liner in a fishing game is a bold boat choice. that free demo should be on

The [USER]/[AI] tag on each decision is the useful part. When something breaks later, the AI-tagged choices are the ones to reopen first, and the user-tagged ones can stay put.
