Engineering
Game desk: Grok Bot orchestrates Claude + Grok Build on your Mac Mini
Local coding agents stall, and you still want one place that watches the whole build.
What hurt
Mike P (@mikepat711) runs a game-building workflow where Grok Bot takes the prompt, delegates across models on a Mac Mini, watches coding agents, and nudges them if they stall. Claude Code / Opus handles story, levels, and engine design; Grok Build / Grok hammers levels, enemies, playtests, and trailer; Bot runs final tests and deploys to Cloudflare when ready. Tip with author-published role split. Not affiliated with xAI.
What to install or create
One orchestrator Bot on the prompt → specialist models on the Mini → Bot final test + deploy.
Bots
No new bot. Follow the first-run steps.
Plugins
None on day one. Follow the first-run steps.
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/mikepat711/status/2106172829171331207 (credit @mikepat711).
- 2Name one orchestrator Grok Bot whose only job is: take your prompt, watch local agents, nudge stalls.
- 3On the Mac Mini (or similar), assign design/story work to a strong coding agent (Claude Code / Opus in Mike’s split) and grindwork to Grok Build.
- 4Tell the orchestrator the finish line (playable build + tests) and that it reports only start + final results to you.
- 5Keep deploy to Cloudflare / commits behind your explicit approve; re-run final tests before ship.
Approval fence
Approve deploys and any Cloudflare / git pushes yourself before the Bot ships.
What to tweak
Steal the watch-and-nudge orchestrator. You only see the first reply and the final ship.
Source
Mike P @mikepat711 · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.