跳过主要内容
GDT
Skill免费GameSkill 出品GameSkill 原创

Godot, One Mechanic at a Time (reference folder, grey box, tested mechanics)

/godot-one-mechanic

A GameSkill original for building a Godot 4 game with an agent in an order that holds up: a reference folder with a style-prompt JSON, a grey box, then one mechanic per prompt in its own script with its own headless playtest, re-running every earlier playtest before the next. Ships templates, checkers for the reference folder and project layout, and a tested 2D example (run and jump, then glide across a gap) whose playtests catch a broken mechanic.

许可证
MIT
出品
GameSkill 出品
下载 ZIP

我们测过

在 Godot 4.7.2 (2D physics, headless playtests) + Python 3 standard library 上通过 35/35 项检查(2026-11-03):能触发、有可运行示例、有截图和自检清单、单一职责、中英文文档齐全。触发检查是把提示词和 skill 描述做匹配,不是真实 agent 运行。

测试报告

GameSkill 测过的版本

GameSkill 为 gameskill.dev 原创编写并测过。ZIP 里是完整的 skill:SKILL.md 及中文版、脚本、可运行示例、测试、自检清单和我们的测试报告。

下载测过的 ZIP(31 KB)路线图:玩法机制

GameSkill 原创,协议 MIT。ZIP 保留 LICENSE 和 CREDITS.md,里面列出了流程灵感来源、CC0 测试素材和第三方库及其协议。

Godot, One Mechanic at a Time (reference folder, grey box, tested mechanics)

自检清单

  • 先写 refs/style.json,每张图写取什么、不取什么 / Write refs/style.json first; every image says what to take and ignore
  • 先灰盒,尺寸写成常量 / Grey box first, sizes as constants
  • 一个提示只加一个机制,一个机制一个脚本 / One mechanic per prompt, one script per mechanic
  • 每个机制的测试同时说明它做什么、为什么需要它 / Each playtest shows what the mechanic does and why it is needed
  • 打开新机制后重跑之前所有测试组 / Re-run every earlier playtest group with the new mechanic on
  • 机制稳定之前不上美术 / No art until the mechanics hold

中文指南

这个 skill 做什么

让 agent 按一个站得住的顺序做 Godot 4 游戏:先建参考图文件夹和风格 JSON,再做灰盒,然后一个提示只加一个机制,每个机制一个脚本、一组无界面试玩测试,加新机制前重跑之前所有测试。附带模板、参考文件夹和项目结构的检查器,以及一个测过的 2D 示例(跑跳,再加滑翔过坑),它的测试能抓到坏掉的机制。

什么时候用

  • 用 agent 开始做 Godot 游戏,希望每一步都被证明后再往下做
  • 加了新机制,旧机制却悄悄坏了
  • 手里有一堆参考图,想让 agent 按它搭出世界

怎么装

下载本页 ZIP,把 godot-one-mechanic/ 放进 agent 的 skills 文件夹:Claude Code 用 .claude/skills/,Codex、Gemini CLI、OpenCode 用 .agents/skills/,Cursor 用 .cursor/skills/,Copilot 用 .github/skills/,Windsurf 用 .windsurf/skills/。也可以直接对 agent 说:Install the skill from https://gameskill.dev/skills/godot-one-mechanic/install.md

最小示例

「悬崖滑翔」灰盒:机制 1 跑和跳,机制 2 下落时按住跳跃滑翔。300 像素的坑,普通跳过不去,滑翔能过去;还有参考图文件夹(代码画的调色板和轮廓草图)和写好的 style.json。

我们怎么测的

在 Godot 4.7.2 无界面模式下跑 14 项试玩测试(机制 1、机制 2、打开机制 2 后重跑机制 1);检查参考文件夹和项目结构的规则;再做两个坏掉的副本:太弱的滑翔被「滑翔过坑」测试抓到,上升也被限速的滑翔只在重跑机制 1 时暴露。最后用 xvfb 截图。结果在 gameskill/test-report.json。

搭配

  • glb-godot-acceptance:上美术时检查 3D 模型
  • game-feel:机制稳定后调手感
  • style-cards:把风格写成可检查的限制

安装

告诉你的 AI

Install the skill from https://gameskill.dev/skills/godot-one-mechanic/install.md

GameSkill 测过的版本

测过的版本装到 .claude/skills/
mkdir -p .claude/skills
curl -fsSL https://gameskill.dev/dl/skills/godot-one-mechanic.zip -o /tmp/gameskill-godot-one-mechanic.zip
unzip -oq /tmp/gameskill-godot-one-mechanic.zip -d .claude/skills
rm /tmp/gameskill-godot-one-mechanic.zip

包含内容

  • The loop: reference folder, grey box, one mechanic per prompt, its playtest, re-run everything
  • templates/: style.json (style-prompt JSON), MECHANICS.md (one row per mechanic), mechanic.gd
  • tools/check_refs.py: every reference image says what to take and ignore; no 'in the style of'
  • tools/check_project.py: one script per mechanic, no rules in the player, a playtest group each, re-runs present
  • Cliff Glider grey box: run and jump, then glide across a 300 px gap, 14 headless playtests

适合

  • Starting a Godot game with an agent so each step is proven before the next
  • Adding a mechanic without silently breaking an earlier one
  • Turning a folder of reference images into a style the agent can follow

不适合

  • A specific mechanic's design: see the mechanic skills
  • Unity or Unreal projects: the scripts and playtests are Godot's

试试这条提示词

提示词
Start my Godot platformer the one-mechanic way: write refs/style.json from my reference images, make a grey box, then add mechanic 1 (run and jump) with its playtests.

关于这个 Skill

Godot, One Mechanic at a Time is a GameSkill original about the order of work when an agent builds a Godot game. A whole game from one prompt tends to be a game where nothing quite works and nobody can say why. This skill has the agent start from a reference folder and a style-prompt JSON, build a grey box, then add exactly one mechanic per prompt, in its own script, with a headless playtest that proves both what it does and why the game needs it, and re-run every earlier playtest before moving on. Art comes after the mechanics hold.

The example, Cliff Glider, is our own grey box: run and jump, then a glide that is the only way across a 300 px gap. Its tests also break the glide on purpose: a glide that slows the rise passes the old jump tests on their own and is only caught when they run again with the glide switched on. The ideas of building a world from a folder of references and prompting one mechanic at a time come from posts by @sorenxet (link only; no code or text was used). The templates, tools and example are ours.

环境要求

  • Godot 4.2+ (tested on 4.7.2); playtests run headless
  • Python 3 standard library for check_refs.py and check_project.py

相关主题

常见问题

基于 Reference folder to world, and one mechanic per prompt (posts, ideas only) (作者 @sorenxet,no licence, idea only, no code or text used)的思路。代码和文字由 GameSkill 编写,ZIP 里的 CREDITS.md 列出所有来源。

搭配使用

作者标注的相关 Skills,或更适合相邻任务的 Skills。

相似 skills