メニュー
Develop, test, build, and deploy Godot 4.x games. Includes GdUnit4 for GDScript unit tests and PlayGodot for game automation and E2E testing. Supports web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | godot |
| version | 1.2.0 |
| description | Develop, test, build, and deploy Godot 4.x games. Includes GdUnit4 for GDScript unit tests and PlayGodot for game automation and E2E testing. Supports web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io. |
Develop, test, build, and deploy Godot 4.x games.
# GdUnit4 - Unit testing framework (GDScript, runs inside Godot)
godot --headless --path . -s res://addons/gdUnit4/bin/GdUnitCmdTool.gd --run-tests
# PlayGodot - Game automation framework (Python, like Playwright for games)
export GODOT_PATH=/path/to/godot-automation-fork
pytest tests/ -v
# Export web build
godot --headless --export-release "Web" ./build/index.html
# Deploy to Vercel
vercel deploy ./build --prod
| GdUnit4 | PlayGodot | |
|---|---|---|
| Type | Unit testing | Game automation |
| Language | GDScript | Python |
| Runs | Inside Godot | External (like Playwright) |
| Requires | Addon | Custom Godot fork |
| Best for | Unit/component tests | E2E/integration tests |
GdUnit4 runs tests written in GDScript directly inside Godot.
project/
├── addons/gdUnit4/ # GdUnit4 addon
├── test/ # Test directory
│ ├── suites/ # Test suites
│ │ └── MyTestSuite.gd # Test suite file
│ └── test_resources/ # Test resources
└── src/ # Source code
# test/suites/MyTestSuite.gd
extends GdUnitTestSuite
func test_example():
var result = 2 + 2
assert_int(result).is_equal(4)
func test_node_creation():
var node = Node.new()
assert_node(node).is_not_null()
node.queue_free()
# Run all tests
godot --headless --path . -s res://addons/gdUnit4/bin/GdUnitCmdTool.gd --run-tests
# Run specific test suite
godot --headless --path . -s res://addons/gdUnit4/bin/GdUnitCmdTool.gd --run-tests --suite MyTestSuite
# Run with verbose output
godot --headless --path . -s res://addons/gdUnit4/bin/GdUnitCmdTool.gd --run-tests --verbose
PlayGodot provides Python-based game automation, similar to Playwright for web applications.
# Install dependencies
pip install -r requirements.txt
# Set Godot path
export GODOT_PATH=/path/to/godot-automation-fork
# tests/test_game.py
from playgodot import Game, GameTest
class TestGame(GameTest):
async def test_player_movement(self):
game = await Game.launch("res://scenes/main.tscn")
# Test player movement
player = game.get_node("Player")
initial_pos = player.position
# Simulate key press
await game.press_key(KEY_RIGHT)
await game.wait(0.5)
# Assert player moved
assert player.position.x > initial_pos.x
await game.close()
# Run all tests
pytest tests/ -v
# Run specific test
pytest tests/test_game.py::TestGame::test_player_movement -v
# Run with coverage
pytest tests/ --cov=src --cov-report=html
# Export web build
godot --headless --export-release "Web" ./build/index.html
# Export with custom template
godot --headless --export-release "Web" ./build/index.html --custom-template path/to/template
# Export Windows
godot --headless --export-release "Windows Desktop" ./build/game.exe
# Export macOS
godot --headless --export-release "Mac OSX" ./build/game.app
# Export Linux
godot --headless --export-release "Linux/X11" ./build/game.x86_64
# Deploy to Vercel
vercel deploy ./build --prod
# Deploy with custom domain
vercel deploy ./build --prod --domain my-game.vercel.app
# Deploy to GitHub Pages
gh-pages -d ./build
# Deploy with custom domain
gh-pages -d ./build --cname my-game.github.io
# .github/workflows/test.yml
name: Test and Deploy
on: [push, pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: godotengine/godot-ci@v3
with:
godot-version: 4.2
- name: Run GdUnit4 tests
run: godot --headless --path . -s res://addons/gdUnit4/bin/GdUnitCmdTool.gd --run-tests
- name: Run PlayGodot tests
run: pytest tests/ -v
- name: Export web build
run: godot --headless --export-release "Web" ./build/index.html
- name: Deploy to Vercel
run: vercel deploy ./build --prod
This skill integrates with the following agents:
Version: 1.2.0 Last updated: 2026-03-10 Integration: Claude Code Game Studios
Define the sensory identity of a game — how it looks, sounds, and feels in service of the vision and pillars. The bridge between design intent and sensory execution. Use this skill when: (1) establishing the visual, audio, and tactile identity for a new project, (2) a game "feels wrong" and the sensory layer may be misaligned with mechanics or vision, (3) pillar changes require aesthetic re-evaluation (bidirectional with Skill 2), (4) defining art direction or audio direction pillars, (5) establishing game feel targets (juice, responsiveness, weight), (6) ensuring sensory coherence across all elements, (7) defining component aesthetics for tabletop (table presence, material quality). Co-equal with Design Pillars (Skill 2) at Tier 2. Medium-agnostic.
Guided game concept ideation — from zero idea to a structured game concept document. Uses professional studio ideation techniques, player psychology frameworks, and structured creative exploration.
Cocos Creator 命令行自动化工具。支持场景管理、资源操作、节点创建、组件绑定、属性设置等常用开发流程。从dev/cocos-skills-main整合的Cocos Creator CLI自动化工具，提供HTTP-based编辑器控制和程序化开发支持。
Game industry competitive analysis framework for product managers. Provides structured methodologies for analyzing competing games, studios, and market positioning. Use when: (1) mapping the competitive landscape for a game genre or product, (2) building feature comparison matrices across competing titles, (3) analyzing positioning, monetization, or UA strategy differences, (4) conducting win/loss analysis on player acquisition and churn, (5) identifying market trends, genre shifts, and platform changes, (6) creating competitive intelligence briefs with web research. Triggers: "competitive analysis", "competitor research", "竞品分析", "竞争对手", "竞品调研", "市场分析", "competitor comparison", "market positioning", "feature matrix", "win loss analysis", "genre analysis", "品类分析", "竞品报告", "市场调研", "对标分析"
Define the fundamental action cycle — what the player does repeatedly and why it stays engaging. The heartbeat of the game. Use this skill when: (1) translating pillars and experience targets into a concrete gameplay cycle, (2) diagnosing why a game feels repetitive or disengaging, (3) designing nested loop structures (moment-to-moment, session, meta/campaign), (4) identifying attrition risk points where players disengage, (5) evaluating whether a proposed mechanic serves the core loop or fragments it, (6) designing how the loop evolves over time to sustain long-term engagement. Medium-agnostic — works for digital, tabletop, and hybrid games.
Meta-skill that wraps the Game Design Skill Suite (21 skills, 8 tiers). Manages change propagation, coherence checking, priority arbitration, and adaptive flow between game design skills. Use this skill when: (1) starting a new game design project and determining which skills to activate, (2) a design change in one area may affect other areas, (3) checking whether all design elements are still aligned with vision and pillars, (4) resolving conflicts between competing design demands, (5) re-entering the design process after a playtest or discovery invalidates assumptions, (6) the designer wants to start from a non-standard entry point (e.g., starting from a mechanic idea rather than vision).