RandallLiuXin/GodotMaker / skills/core/project-scaffold
project-scaffold
VerifiedGenerate a new Godot game project with standardized ECS structure and tooling. Use when starting a new game: "create a project", "set up a new game", "scaffold", "initialize", "new project", "start building", "let's make it". Triggers after game-planner produces a confirmed plan, or when the user provides a game name + genre directly. Even for simple requests like "make me a new Godot project", use this skill to ensure proper ECS structure. Creates directory structure, project.godot, CLAUDE.md, gecs World setup, addon stubs, and template source files based on the game plan or user input.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.2 KB |
| references/addons.md | markdown | 3.5 KB |
| references/project_settings.md | markdown | 2.9 KB |
| templates/claude.md.tmpl | other | 2.5 KB |
| templates/component.tmpl | other | 239 B |
| templates/gitignore.tmpl | other | 198 B |
| templates/main_scene.tmpl | other | 66 B |
| templates/project.godot.tmpl | other | 1.2 KB |
| templates/system.tmpl | other | 423 B |
| templates/test_example.tmpl | other | 388 B |
| templates/world_scene.tmpl | other | 127 B |
references/addons.md
View on GitHub# Addon Installation
Every GodotMaker project requires these dependencies.
Install them after scaffold, before running headless-build or tests.
## Version Compatibility — MANDATORY
Read the active runtime's `config/addon_versions.json` to determine the
correct version for each addon:
- Claude Code: `.claude/config/addon_versions.json`
- Codex: `.agents/config/addon_versions.json`
- OpenCode: `.opencode/config/addon_versions.json`
- Pi: `.pi/config/addon_versions.json`
The JSON maps Godot versions to compatible addon versions. You MUST use the
exact tag specified.
**Steps:**
1. Detect Godot version: `godot --version` (e.g., "4.4.stable")
2. Extract major.minor (e.g., "4.4")
3. Look up the matching entry in `addon_versions.json` → `godot_versions["4.4"]`
4. For each addon, download the exact `tag` from the `repo`
If the Godot version is not in the mapping, use the closest lower version. If no match exists, report to the user — do NOT guess versions.
## Download Method
For each addon in the version mapping, install the addon-only directory:
```bash
# Clone specific tag outside addons/, copy addon subdirectory, clean up.
git clone --depth 1 --branch {tag} https://github.com/{repo}.git .godotmaker/scratch/{addon_name}
cp -r .godotmaker/scratch/{addon_name}/{install_path}/ {install_path}/
rm -rf .godotmaker/scratch/{addon_name}
```
Required copy sources:
- `addons/gecs/` from the source repo's `addons/gecs/`
- `addons/gdUnit4/` from the source repo's `addons/gdUnit4/`
- `addons/godot_e2e/` from the source repo's `addons/godot_e2e/`
Do not clone the full source repository directly into `addons/gecs/`,
`addons/gdUnit4/`, or `addons/godot_e2e/`.
After copying each addon:
1. Confirm `plugin.cfg` exists in the copied addon root.
2. Confirm `project.godot` does not exist in the copied addon root.
3. For gdUnit4, confirm `bin/GdUnitCmdTool.gd` and
`src/core/runners/GdUnitTestCIRunner.gd` exist.
## Post-Download Configuration
### gecs (ECS Framework)
If `"plugin": true` in the mapping:
- Add to `[editor_plugins]` in project.godot:
```
[editor_plugins]
enabled=PackedStringArray("res://addons/gecs/plugin.cfg")
```
### gdUnit4 (Test Framework)
If `"plugin": true` in the mapping:
- Add to `[editor_plugins]` in project.godot:
```
enabled=PackedStringArray("res://addons/gecs/plugin.cfg", "res://addons/gdUnit4/plugin.cfg")
```
### godot-e2e (E2E Testing)
If `"plugin": true` in the mapping:
- Add to `[editor_plugins]` in project.godot alongside gecs and gdUnit4:
```
enabled=PackedStringArray("res://addons/gecs/plugin.cfg", "res://addons/gdUnit4/plugin.cfg", "res://addons/godot_e2e/plugin.cfg")
```
Ensure `AutomationServer` is registered once in `[autoload]`:
```
AutomationServer="*res://addons/godot_e2e/automation_server.gd"
```
## godot-mcp (Runtime Debug Server)
Not a Godot addon — an npm package registered with Claude Code.
```bash
claude mcp add godot -e GODOT_PATH="<path_to_godot_executable>" -- npx @coding-solo/godot-mcp
```
This is handled by publish.sh/ps1 during project setup.
## Verification
After all addons are installed:
```bash
godot --headless --quit 2>&1
```
No `SCRIPT ERROR:` lines means success. Common errors:
- `World` class not found → gecs not installed or not enabled
- `GdUnitRunner` error → gdUnit4 version mismatch with Godot version
- `GdUnitTestCIRunner` not found -> reinstall the gdUnit4 addon-only
directory and run `godot --headless --import`
- `AutomationServer` error → godot-e2e plugin not enabled or addon files missing
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |