godogen

分类: 内容与多媒体 | 上传者: htdt | 下载: 0 | 版本: v1.0（最新）

This skill should be used when the user asks to "make a game", "build a game", "generate a game", or wants to generate or update a complete Godot game from a natural language description. --- # Game Generator — Orchestrator Generate and update Godot games from natural language. ## Capabilities Read each sub-file from `${CLAUDE_SKILL_DIR}/` when you reach its pipeline stage. | File | Purpose | |------|---------| | `visual-target.md` | Generate reference image anchoring art direction | | `decomposer.md` | Decompose game into a development plan (`PLAN.md`) | | `scaffold.md` | Design architecture and produce compilable Godot skeleton | | `asset-planner.md` | Decide what assets the game needs within a budget | | `asset-gen.md` | Generate PNGs (Gemini) and GLBs (Tripo3D) from prompts | ## Pipeline ``` User request | +- Check if PLAN.md exists (resume check) | +- If yes: read PLAN.md, STRUCTURE.md, MEMORY.md -> skip to task execution | +- If no: continue with fresh pipeline below | +- Generate visual target -> reference.png + ASSETS.md (art direction only) +- Decompose into tasks -> PLAN.md +- Design architecture -> STRUCTURE.md + project.godot + stubs | +- If budget provided (and no asset tables in ASSETS.md): | +- Plan and generate assets -> ASSETS.md + updated PLAN.md with asset assignments | +- For every task in PLAN.md: | +- Set `**Status:** pending` | +- Fill `**Targets:**` with concrete project-relative files expected to change | (e.g. scenes/main.tscn, scripts/player_controller.gd, project.godot) | inferred from task text + scene/script mappings in STRUCTURE.md | +- Show user a concise plan summary (game name, numbered task list) | +- Find next ready task (pending, deps all done) +- While a ready task exists: | +- Update PLAN.md: mark task status -> in_progress | +- Skill(skill="godot-task") with task block | +- Mark task completed in PLAN.md OR replan based on the outcome, summarize to user | +- git add . && git commit -m "Task N done" |

更新日志: Source: GitHub https://github.com/htdt/godogen

目录结构

当前层级: skills/godogen/

📁 tools/
- 📄 asset_gen.py 10.4 KB
- 📄 rembg_matting.py 6.8 KB
- 📄 requirements.txt 69 B
- 📄 spritesheet_slice.py 5.4 KB
- 📄 spritesheet_template.py 3.1 KB
- 📄 tripo3d.py 5.1 KB
📄 asset-gen.md 8.6 KB
📄 asset-planner.md 6.6 KB
📄 decomposer.md 9.5 KB
📄 scaffold.md 10.1 KB
📄 SKILL.md 4.0 KB
📄 visual-target.md 1.2 KB

SKILL.md

---
name: godogen
description: |
  This skill should be used when the user asks to "make a game", "build a game", "generate a game", or wants to generate or update a complete Godot game from a natural language description.
---

# Game Generator — Orchestrator

Generate and update Godot games from natural language.

## Capabilities

Read each sub-file from `${CLAUDE_SKILL_DIR}/` when you reach its pipeline stage.

| File | Purpose |
|------|---------|
| `visual-target.md` | Generate reference image anchoring art direction |
| `decomposer.md` | Decompose game into a development plan (`PLAN.md`) |
| `scaffold.md` | Design architecture and produce compilable Godot skeleton |
| `asset-planner.md` | Decide what assets the game needs within a budget |
| `asset-gen.md` | Generate PNGs (Gemini) and GLBs (Tripo3D) from prompts |

## Pipeline

```
User request
    |
    +- Check if PLAN.md exists (resume check)
    |   +- If yes: read PLAN.md, STRUCTURE.md, MEMORY.md -> skip to task execution
    |   +- If no: continue with fresh pipeline below
    |
    +- Generate visual target -> reference.png + ASSETS.md (art direction only)
    +- Decompose into tasks -> PLAN.md
    +- Design architecture -> STRUCTURE.md + project.godot + stubs
    |
    +- If budget provided (and no asset tables in ASSETS.md):
    |   +- Plan and generate assets -> ASSETS.md + updated PLAN.md with asset assignments
    |
    +- For every task in PLAN.md:
    |   +- Set `**Status:** pending`
    |   +- Fill `**Targets:**` with concrete project-relative files expected to change
    |     (e.g. scenes/main.tscn, scripts/player_controller.gd, project.godot)
    |     inferred from task text + scene/script mappings in STRUCTURE.md
    |
    +- Show user a concise plan summary (game name, numbered task list)
    |
    +- Find next ready task (pending, deps all done)
    +- While a ready task exists:
    |   +- Update PLAN.md: mark task status -> in_progress
    |   +- Skill(skill="godot-task") with task block
    |   +- Mark task completed in PLAN.md OR replan based on the outcome, summarize to user
    |   +- git add . && git commit -m "Task N done"
    |   +- Find next ready task
    |
    +- Summary of completed game
```

PLAN.md task `**Status:**`: one of `pending`, `in_progress`, `done`, `done (partial)`, `skipped`.

## Running Tasks

Each task runs via `Skill(skill="godot-task")` which auto-forks into a sub-agent with clean context. Pass the full task block from PLAN.md as the skill argument:

```
Skill(skill="godot-task") with argument:
  ## N. {Task Name}
  - **Status:** in_progress
  - **Targets:** scenes/main.tscn, scripts/player_controller.gd
  - **Goal:** ...
  - **Requirements:** ...
  - **Verify:** ...
```

## Mid-Pipeline Recovery

- **Reset scenes/scripts** — regenerate project skeleton when a task has corrupted or outgrown the architecture.
- **Rewrite the plan** — edit PLAN.md when a task reveals the approach is wrong or new requirements emerge.
- **Generate or regenerate assets** — create new assets or fix broken ones mid-run.

## Visual QA

Visual QA runs inside godot-task — each task handles its own VQA cycle. The task agent reports a VQA report path alongside screenshots. **Never ignore a fail verdict** — always act on it before marking a task done.

- **pass/warning** — move on.
- **fail** — godot-task already attempted up to 3 fix cycles. Read its failure report (includes VQA issues and root cause hypothesis) and decide:
  - **Replan** — reset architecture, rewrite plan, and/or regenerate assets if the root cause is upstream.
  - **Escalate** — surface the issue to the user if you can't determine the right fix.

The final task in PLAN.md is a presentation video — a script that showcases gameplay in a ~30-second cinematic MP4.

## Debugging

If a task reports failure or you suspect integration issues:
- Read `MEMORY.md` — task execution logs discoveries and workarounds
- Read screenshots in `screenshots/{task_folder}/`
- Run `timeout 30 godot --headless --quit 2>&1` to check cross-project compilation

登录后下载/点赞/收藏 ❤ 119 | ★ 0

godogen

目录结构

SKILL.md

举报内容

提示