Unitygen: skills that build Unity projects with MCP + OpenRouter

Example prompts: demo_prompts.md

Describe the game you want. A staged pipeline plans architecture, generates art, implements C# and scenes through the Unity Editor (MCP), captures screenshots, and runs vision QA via OpenRouter. Output is a real Unity project under Assets/.

• Two skills — unitygen (orchestrator) and unity-task (per-task executor, forked context in Claude Code).
• Unity MCP — scenes, GameObjects, scripts, console, screenshots against a live Editor.
• OpenRouter — image generation and vision QA (OPENROUTER_API_KEY, optional OPENROUTER_IMAGE_MODEL / OPENROUTER_VISION_MODEL).
• Tripo3D — optional image-to-GLB for 3D (TRIPO3D_API_KEY).
• Python tools in skills/unitygen/tools/ (asset_gen.py, rembg, sprite pipeline).

• Unity project + Unity MCP connected to the agent session (e.g. Cursor).
• Python 3 + pip install -r skills/unitygen/tools/requirements.txt
• API keys: copy .env.example to .env (repo root or any parent directory of your shell cwd) and fill in values. asset_gen.py and visual_qa.py load .env automatically via python-dotenv (first match walking up from current working directory). Required: OPENROUTER_API_KEY; for 3D mesh generation: TRIPO3D_API_KEY.
• Claude Code (or another client that supports skills / sub-agents) for published game folders.

This repo is the skill source. Publish into a Unity project directory:

./publish.sh ~/my-unity-game          # uses teleforge.md as CLAUDE.md
./publish.sh ~/my-unity-game local.md

Open the target in your agent IDE, enable Unity MCP, run /unitygen, and describe the game.

• Budget and asset CLI behavior match the previous generator; ledger entries use openrouter_image for image calls.
• Long runs suit a VM; GPU helps Unity Play Mode and captures, not the LLM.
• Default teleforge.md targets Teleforge + Telegram MCP — swap CLAUDE.md if unused.

Follow progress: @alex_erm