Claude4Godot — AI skill for Claude Code
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
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 and tests.
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 ★
- AI Second Brain — Build a living, searchable AI second brain from your ChatGPT, Claude, and research history - Karpathy-style 147 ★
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
Related Skills
Claude Godot Maintainer
A Claude AI skill for maintaining GitHub repositories and developing Godot Engine projects, with official docu
Claude Skills Library
520 drop-in skills for Claude across 45 categories: coding, decision-making, gym, game dev (Godot, Unity, Unre
Jev Linkmap
Rebuild a site's internal link map in seconds with Jev, race Claude Opus 5 on the same queue, and let a deep m
Brain Tree OS
Build a local-first project management system for AI agents with structured knowledge bases, execution plans,
Planning Doc Rules
Ten rules for writing a planning document — drop-in CLAUDE.md / AGENTS.md system prompt that turns any AI agen
Multipov Plan
Run a multi-agent design-doc review on $ARGUMENTS (path to a markdown design doc, typically docs/plans/YYYY-MM
Related Agents
Game Developer
Game development across all platforms (PC, Web, Mobile, VR/AR). Use when building games with Unity, Godot, Unr
Blueprint Agent
Generates docs/BLUEPRINT.md — a living map of the project covering stack, architecture diagram, API inventory,
Documentation Curator
Maintain living documentation, generate API docs, and ensure doc-code synchronization.