godogen

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

当用户要求“制作游戏”、“构建游戏”、“生成游戏”，或者想要从自然语言描述生成或更新完整的 Godot 游戏时，应该使用此技能。 --- # 游戏生成器 — Orchestrator 从自然语言生成和更新 Godot 游戏。 ## 功能当到达管道阶段时，从 `${CLAUDE_SKILL_DIR}/` 读取每个子文件。 |文件 |目的| |------|---------| | `视觉目标.md` |生成锚定艺术方向的参考图像 | | `decomposer.md` |将游戏分解为开发计划（`PLAN.md`） | | `脚手架.md` |设计架构并生成可编译的 Godot 骨架 | | `资产规划器.md` |在预算内决定游戏需要哪些资产 | | `asset-gen.md` |根据提示生成 PNG (xAI Grok) 和 GLB (Tripo3D) | | `rembg.md` |背景去除指南 — 在任何 rembg 操作之前阅读 | | `android-build.md` | Android APK 导出 — 当用户请求 Android 构建时读取 | ## 管道 ``` 用户请求 | +- 检查 PLAN.md 是否存在（继续检查）| +- 如果是：读取 PLAN.md、STRUCTURE.md、MEMORY.md -> 跳到任务执行 | +- 如果否：继续使用下面的新管道 | +- 生成视觉目标 -> reference.png + ASSETS.md（仅限艺术指导） +- 分解为任务 -> PLAN.md +- 设计一个架构 -> STRUCTURE.md + project.godot + 存根 | +- 如果提供预算（并且 ASSETS.md 中没有资产表）：| +- 规划和生成资产 -> ASSETS.md + 使用资产分配更新了 PLAN.md | +- 对于 PLAN.md 中的每个任务： | +- 设置`**状态：**待处理` | +- 用预计要更改的具体项目相关文件填充“**目标：**”| （例如。场景/main.tscn、脚本/player_controller.gd、project.godot) |从 STRUCTURE.md 中的任务文本 + 场景/脚本映射推断+- 向用户显示简洁的计划摘要（游戏名称、编号任务列表）| +- 查找下一个就绪任务（待处理，全部完成） +- 当存在就绪任务时： | +- 更新 PLAN.md：标记任务状态 -> in_progress | +- 技能(技能=“去

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

目录结构

当前层级: tree/master/skills/godogen/

📁 tools/
- 📄 asset_gen.py 9.4 KB
- 📄 find_loop_frame.py 2.0 KB
- 📄 grid_slice.py 1.9 KB
- 📄 rembg_matting.py 11.0 KB
- 📄 requirements.txt 98 B
- 📄 tripo3d.py 5.1 KB
📄 android-build.md 3.2 KB
📄 asset-gen.md 9.9 KB
📄 asset-planner.md 9.8 KB
📄 decomposer.md 9.5 KB
📄 rembg.md 3.7 KB
📄 scaffold.md 10.3 KB
📄 SKILL.md 4.3 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 (xAI Grok) and GLBs (Tripo3D) from prompts |
| `rembg.md` | Background removal guide — read before any rembg operation |
| `android-build.md` | Android APK export — read when user requests an Android build |

## 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
    |
    +- If user requested Android app:
    |   +- Read android-build.md, add ETC2/ASTC to project.godot, create export_presets.cfg, export APK
    |
    +- 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

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

godogen

目录结构

SKILL.md

举报内容

提示