Freakling

Claude4Godot — AI skill for Claude Code

AI community

A drop-in workflow for Godot games built with Claude Code and Claude Cowork: a living design doc, task queue, system map and agent personas that keep you in charge of design while the AI builds, plans.

How to install Claude4Godot

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Freakling/Claude4Godot and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude4Godot does

Alternatives in AI

Agenttrail — Local observability map for AI coding agents 269 ★
Glade MCP — Connect any MCP-compatible AI client (Claude Code, Cursor, Windsurf) to Unity or Godot 201 ★
Openclaw Guide — 开源OpenClaw中文文档站，OpenClaw中文指南，支持小龙虾 AI 智能体安装部署、消息渠道接入、Agent 架构、Skills 技能配置、模型提供商、CLI 命令参考、网关运维、安全沙箱等全方位文档 159 ★

README

Claude4Godot

A drop-in workflow for building Godot games with two Claude agents and one human:

Who	Where	Responsible for
You (the developer)	—	Design, balance, art direction and priorities; playing and playtesting; approving commits and pushes. You have the final say on everything.
Claude Cowork	Claude desktop app	Design sessions, GDD revisions, planning `TASKS.md`, keeping the docs aligned, processing playtests
Claude Code	Terminal, IDE or desktop app	GDScript, scenes, `.tres` data, running Godot (the headless check) and git (commits and pushes, with your approval)

Running Godot and git is **Claude Code's job only**. Cowork doesn't commit: when it changes files, it lists them and gives you a ready-to-paste commit prompt for Claude Code. Neither agent makes design decisions or picks final balance numbers — those are yours.

The agents coordinate through a small set of plain Markdown files — a design document, a task queue, a system map, a router and a set of personas — so either agent can pick up where the other left off, and so you always know what's decided, what's open and what's next.

What's in this folder

Claude4Godot/
├── README.md          ← this file (for you)
├── ONBOARDING.md      ← the install-and-adapt script Cowork follows
├── .gdignore          ← keeps Godot from importing this folder
└── template/          ← the files that get installed into your project root
    ├── CLAUDE.md              entry point for every agent session
    ├── AGENTS.md              router: which doc/section to open for which task + ground rules
    ├── TASKS.md               the work queue + bug table + archive
    ├── SYSTEMS.md             what exists in code: systems, files, dependencies
    ├── README.md              skeleton for your project README (status, roadmap, responsibility split)
    ├── design/gdd.md          Game Design Document skeleton with the revision + open-question process