菜单
Scaffolds a minimal Godot mini-game project from a reusable infrastructure-only template. Use when starting a Godot 4.2+ mini-game that needs headless tests, Web export defaults, canvas shell, telemetry helpers, and procedural audio primitives.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Converts a working mini-game into a complete arcade game by adding round structure, ceremony screens (READY / round clear / death / game over), a score economy (extends, round bonuses, initials entry, high-score table), and jingle/SE separation. Use when a playable game with a verified core loop still "feels like a minigame" and needs arcade completeness — rounds or waves, 1UP extends, name entry, attract mode. Not for designing the core mechanic itself (use designing-mini-games first).
Designs original, compact mini-games — rules, controls, scoring, hazards, and difficulty curves — for any input scheme, including one-button (tap / hold / release) games. Use when defining a new mini-game concept, converting creative constraints or seeds into mechanics, choosing an input scheme, checking state-variable necessity, or preventing idle, hold-only, or mashing play from becoming optimal.
Translates game design prose into engine-neutral implementation invariants and validation checks. Use when implementing or reviewing game mechanics where idle, hold-only, mashing, spam, safe waiting, or repeated scoring pulses must be prevented from dominating skilled play.
Creates or repairs browser mini-games specifically using crisp-game-lib. Use only when the user explicitly asks for crisp-game-lib or the existing project already uses it; skip for Godot, Unity, Phaser, canvas-only, or unspecified engine requests.
Batch-generates, evaluates, and specs multiple fixed-screen arcade game concepts in the style of 1978-1983 cabinets. Use when asked to brainstorm several new arcade games at once, produce a concept slate to choose from, or turn era/hardware constraints into ranked concepts plus implementation specs. For hardening a single already-chosen concept, use designing-mini-games instead.
Verifies that implemented game mechanics match their spec by injecting game state into a live headless browser and asserting the resulting transitions (phase changes, scoring formulas, gates, resets). Use after implementing or changing a specific mechanic in a browser game — when a smoke test (runtime health) passes but spec conformance is unverified, or when a mechanic is too rare or slow to reach through organic play. Not for crash detection (use smoke-testing-web-games) or play-quality judgment (use evaluating-gameplay-balance).
| name | scaffolding-godot-mini-games |
| description | Scaffolds a minimal Godot mini-game project from a reusable infrastructure-only template. Use when starting a Godot 4.2+ mini-game that needs headless tests, Web export defaults, canvas shell, telemetry helpers, and procedural audio primitives. |
Use this skill to initialize a Godot mini-game from the bundled base project.
Template path:
assets/godot-base/Core rules:
main.gd as orchestration and split responsibilities into focused scripts.project.godot, export_presets.cfg, and web/custom_shell.html together.custom_template/debug and custom_template/release to absolute local paths when using project-local XDG directories.Canonical scaffold command:
PROJECT_DIR=tmp/games/<slug>
mkdir -p "$PROJECT_DIR"
cp -R .agents/skills/scaffolding-godot-mini-games/assets/godot-base/. "$PROJECT_DIR"/
mkdir -p "$PROJECT_DIR/logs" "$PROJECT_DIR/build/web"
This copies the template contents directly into <PROJECT_DIR>. If <PROJECT_DIR> already contains files, inspect it before copying and do not overwrite unrelated work unless the user explicitly asked for a fresh scaffold.
Post-copy validation:
The XDG preconditions from running-headless-godot ("Required rules" — always set project-local XDG_DATA_HOME / XDG_CONFIG_HOME / XDG_CACHE_HOME) apply here too. The simplest way is to set them inline before the validation pair:
export XDG_DATA_HOME="$PROJECT_DIR/.godot-xdg/data"
export XDG_CONFIG_HOME="$PROJECT_DIR/.godot-xdg/config"
export XDG_CACHE_HOME="$PROJECT_DIR/.godot-xdg/cache"
mkdir -p "$XDG_DATA_HOME" "$XDG_CONFIG_HOME" "$XDG_CACHE_HOME"
godot --headless --path "$PROJECT_DIR" --version 2>&1 | tee "$PROJECT_DIR/logs/version.log"
timeout 5s godot --headless --path "$PROJECT_DIR" 2>&1 | tee "$PROJECT_DIR/logs/smoke_main_initial.log"
Pass criteria for the validation pair:
version.log shows a Godot 4.2+ version line and no "Project file not found" / GDScript parse errors.smoke_main_initial.log shows clean boot to the timeout-induced exit (exit code 124 from timeout is expected here — the template has no quit hook). Treat any SCRIPT ERROR / ERROR: line outside a project-known-warning whitelist as failure.Validation milestones:
res://tools/tests/run_tests.gd before claiming logic, telemetry, scoring, or balance coverage.build/web/index.html.After copying, continue with scene editing, runtime verification, and Web export through a reproducible headless-Godot workflow (the XDG preconditions above apply throughout).
Read assets/godot-base/TEMPLATE_SCOPE.md before changing the template itself.
Read references/visual-implementation-patterns.md when implementing a visual direction from directing-game-visuals in Godot.
Read references/godot-balance-pattern-examples.md when applying evaluating-gameplay-balance patterns in GDScript.