GD Agentic Skills: The Godot 4 Mastery Ecosystem

---

💬 A Message from the Creator (Divergent AI)

March 19, 2026

Hey everyone, Divergent AI here! I’m super happy that I’m seeing the project getting some love. It’s motivated me to come back at it with a really strong update for you all. I’ve spent many hours working on updating all Domain Skills to be completely packed with top expert-level knowledge as learned directly from the robot’s mouth—the Godot documentation.

---

📜 Updates

• Godot 4.7 Director’s Cut: Full library upgrade to Godot 4.7+ — AreaLight3D, HDR output, Asset Store, built-in virtual joystick, and migration digest for 4.6→4.7 projects.
• Domain Skills: Renamed “Micro-Skills” to Domain Skills — 92 modular topic skills, each with 4.7 baseline and targeted migration deltas.
• godot-master: Full mirror sync of domain skill references and bundled scripts for 4.7.
• Persona Squad: Anara, Aurelius, and Builder updated for 4.7 scoring, never-lists, and GODOT_PATH CLI overrides.

---

---

📍 Quick Navigation

---

The Philosophy

Godot Agentic Skills is a high-density, Agent-First knowledge library for Godot 4.7+—designed as an external “Long-Term Memory” (LTM) for AI Coding Agents. It provides structured, deterministic patterns for professional game and application engineering.

Unlike generic AI responses, every skill in this repository follows strictly defined Godot 4 best practices, architectural patterns, and performance optimization techniques refined by shipping real products.

If this project helps your development or empowers your agents, please give it a star! 🌟

---

⚡ Quick Start

Choose your path to avoid a “Context Storm” (overloading your agent with too many instructions at once).

🏆 Path A: The Architect (New or Existing Projects)

If you are starting a new project OR you have an existing project that needs to be “checked” and brought up to date with modern Godot 4 standards, install the Godot Master hub.

npx skills add thedivergentai/gd-agentic-skills/skills/godot-master

🧩 Path B: The Specialist (Existing Projects)

If you need a specific feature (e.g., 2D movement, inventory), install only that Domain Skill.

npx skills add thedivergentai/gd-agentic-skills/skills/godot-characterbody-2d

[!DANGER] NEVER use the --all flag when installing this repository (e.g., npx skills add ... --all). This is an “Instant No-No” that will cause an unrecoverable Context Storm by forcing your agent to read every single metadata entry in the library.

---

🧭 Agent Installation Rubric

Use this when installing via the skills CLI, or when an agent is reading this README after a repo clone (DIA path) instead of a normal plugin install.

Rules

1. Preferred install: npx skills add thedivergentai/gd-agentic-skills/skills/godot-master -g -a -y (swap the skill path for a Domain Skill when needed).
2. Verify: npx skills list -g -a
3. Restart the host agent after install — most agents load skills once at session start.
4. Clone / DIA path (no npx skills add): query skills_index.json, then read skills//SKILL.md with the agent’s file tool. Do not hand-symlink into host skill dirs unless the user asks for that.
5. Canonical store: ~/.agents/skills/ is the CLI’s shared copy; per-agent discovery paths differ by design.

Troubleshooting

• Skill installed but missing in the agent → confirm with npx skills list, re-run with the correct -a , then restart the agent.
• Do not treat a manual Claude-only symlink into ~/.claude/skills/ as the default fix — that only helps one host.

---

🧠 Context Management: Performance Guidelines

To keep your AI agent fast and accurate, follow these “Expert Efficiency” rules:

1. The “Power of One” Rule

Either use godot-master (which orchestrates the other 95 skills via references) OR use individual Domain Skills.

• Godot Master is an “Orchestrator” skill. It is dense (~15k tokens) but provides a complete blueprint. Use it when the “Big Picture” matters.
• Domain Skills are “Surgical” skills (~2-5k tokens). They are fast, reliable, and keep the agent focused on one specific API.

2. Why “Install All” Fails

Installing 96 skills simultaneously creates a “Metadata Flood”:

• Token Bleed: ~15,000 tokens are “permanently” used just to tell the agent which skills exist.
• Instruction Conflicts: Having multiple overlapping expert instructions (e.g., 20+ different genre blueprints) can cause the agent to lose its specific focus.
• Reasoning Lag: The model has to sift through 100+ KB of text before deciding what to do.

3. Repository Clones vs. Plugin Installs

• Plugin Install (npx skills add): Copies/links the skill into your agent’s skill directory (see Agent Installation Rubric). The agent can then discover it automatically. This is why installing too many at once causes a “Context Storm.”
• Repository Clone: If you merely clone this repo to a folder (e.g., Downloads/GDSkills), the agent will NOT auto-load skills unless you are working inside that directory. Use skills_index.json + read each SKILL.md with the agent’s file tool (DIA loop below).

---

🏆 Godot Master — Your Lead Architect

The godot-master skill is the crown jewel of this repository—a consolidated expert library that orchestrates all 96 specialized skills into a unified architectural framework.

🎯 What Makes Godot Master Special?

Unlike individual Domain Skills that focus on isolated features, godot-master is your system architect. It provides:

📚 Comprehensive Knowledge Base

• 96 Reference Documents: Complete markdown guides for every skill, from foundations to advanced genres
• 982 Unique Production Scripts: Battle-tested, production-ready GDScript implementations
• 11 Workflow Patterns: Step-by-step architectural workflows (scaffolding, entity orchestration, persistence, optimization, multiplayer, Builder CLI scene builds, etc.)

🧠 Expert Frameworks

• Architectural Decision Matrix: Choose the right pattern for your project (component-driven, event-driven, resource-streaming, deterministic networking)
• 15 Anti-Patterns: Explicit “NEVER DO THIS” rules with non-obvious explanations (e.g., why get_tree().root.get_node() breaks, why load() in _process kills performance)
• Performance Budgets: Concrete numbers for mobile/desktop targets (draw calls, triangle counts, script time)
• Server API Patterns: Expert escape hatch for 10K+ entities using RenderingServer/PhysicsServer RIDs

🏗️ The Layer Cake Architecture

Godot Master enforces a signal-based separation of concerns:

graph TD
    UI[🎨 PRESENTATIONUI / VFX / Audio] -->|Signals ⬆️| LOGIC[⚙️ LOGICState Machines / Controllers]
    LOGIC -->|Signals ⬆️| DATA[💾 DATAResources / .tres / Stats]
    DATA -->|Signals ⬆️| INFRA[🌐 INFRASTRUCTUREAutoloads / Signal Bus / Managers]
    
    style UI fill:#1f2937,stroke:#58A6FF,stroke-width:2px,color:#fff
    style LOGIC fill:#1f2937,stroke:#79C0FF,stroke-width:2px,color:#fff
    style DATA fill:#1f2937,stroke:#A371F7,stroke-width:2px,color:#fff
    style INFRA fill:#1f2937,stroke:#F778BA,stroke-width:2px,color:#fff

Critical Rule: Signals travel UP only. Presentation layer never modifies Data directly. Infrastructure speaks exclusively through signals.

🔄 When to Use Godot Master vs Domain Skills

flowchart LR
    START([New Task]) --> Q1{Starting anew project?}
    Q1 -->|Yes| MASTER[Use godot-master]
    Q1 -->|No| Q2{Need architecturalguidance?}
    Q2 -->|Yes| MASTER
    Q2 -->|No| Q3{Building acomplete system?}
    Q3 -->|Yes| MASTER
    Q3 -->|No| MICRO[Use Domain Skill:targeted implementation]
    
    MASTER --> DESC1[✓ Full workflow context✓ Decision frameworks✓ Anti-patterns✓ Performance budgets]
    MICRO --> DESC2[✓ Quick implementation✓ Focused feature✓ Standalone pattern]
    
    style START fill:#1f2937,stroke:#58A6FF,stroke-width:3px,color:#fff
    style MASTER fill:#0d1117,stroke:#58A6FF,stroke-width:3px,color:#79C0FF
    style MICRO fill:#0d1117,stroke:#A371F7,stroke-width:3px,color:#F778BA
    style DESC1 fill:#1f2937,stroke:#58A6FF,stroke-width:2px,color:#fff
    style DESC2 fill:#1f2937,stroke:#A371F7,stroke-width:2px,color:#fff

Use godot-master when:

• Starting a new Godot project from scratch
• Auditing an existing project to find anti-patterns or standards violations
• Designing game or application architecture
• Building entity/component systems
• Debugging performance or physics issues
• Choosing between 2D/3D approaches
• Implementing multiplayer
• Optimizing draw calls or script time
• Porting between platforms

Use Domain Skills when:

• Adding a specific feature to an existing codebase
• Learning a targeted Godot API pattern
• Implementing standalone functionality (UI component, particle effect, save system)

📖 Access Godot Master

# Skill path
skills/godot-master/SKILL.md

# Contains
├── 91 reference markdown files (references/)
├── 185 production scripts (scripts/)
└── Complete architectural decision trees

---

🧩 Domain Skills — Bite-Size Power

Individual Domain Skills are modular add-ons for targeted functionality. Each is atomic, self-contained, and production-ready—perfect for when you need a specific implementation pattern without the full architectural context.

Think of Domain Skills as your component library: Drop them into your project for instant, expert-level functionality.

📂 Full Skill Index

All skills are catalogued in the machine-readable skills_index.json with keywords, descriptions, and dependency chains.

[!NOTE] This JSON index is a repository-level file and is only present if you have cloned the source repository.

---

🤖 For Agents — The Discovery-Ingestion-Application Protocol

AI agents must follow the DIA loop for maximum quality:

1️⃣ Discovery

Query skills_index.json to find the skill matching the user’s intent.

Example: User wants “smooth character movement” → Agent finds godot-characterbody-2d and godot-tweening.

2️⃣ Ingestion

CRITICAL: Agents MUST NOT implement from general training data alone.

Required: Read the skill’s SKILL.md with the agent’s file tool to catch Godot 4-specific nuances (e.g., AudioServer.get_time_since_last_mix() for rhythm sync, StringName for O(1) dictionary lookups).

For complex projects: Load godot-master for architectural workflows and anti-patterns.

3️⃣ Application

Follow the Skill Chain documented in the skill header. Apply patterns recursively, starting from the deepest dependency.

Example Workflow:

User: "Build a player controller"
Agent: Query skills_index.json → Find godot-characterbody-2d
Agent: Read godot-characterbody-2d/SKILL.md → See dependencies: godot-composition, godot-state-machine-advanced
Agent: Read godot-composition/SKILL.md → Implement component architecture first
Agent: Read godot-state-machine-advanced/SKILL.md → Build state machine layer
Agent: Return to godot-characterbody-2d → Implement movement with components + states

🚨 Anti-Erosion Policy

Documentation MUST remain in sync with implementation. If a Godot 4 API changes, update the relevant SKILL.md immediately.

---

🏗️ Infrastructure Integration

Programmatic Building (godot-builder)

Scene scaffolding and headless automation go through godot-builder (also mirrored in godot-master Workflow 11). Use Godot CLI scripts such as create_scene.py, add_node.py, and run_project.py.

Project Standards

All code follows Godot 4.7+ conventions:

• Static typing: func move(vec: Vector2) -> void:
• Signal / Callable / Tween (Godot 4 syntax)
• StringName for performance-critical lookups
• Component composition over deep inheritance

---

🤝 Contributing

We welcome contributions from developers and agents!

📖 Read the full contribution guide: CONTRIBUTING.md

Quick Guidelines:

• Every skill must provide Expert Knowledge Delta (not tutorials)
• Include anti-patterns with non-obvious explanations
• Code must be Godot 4.7+ native, statically typed
• Scripts must parse without warnings

Submit: Open an issue with [Request] tag or submit a PR describing the knowledge delta your skill adds.

---

⭐ Star History

If this project accelerates your Godot development or empowers your AI agents, consider starring the repository! ⭐

---

📊 Repository Stats

---

💖 Sponsorship & Support

We are seeking financial sponsors and infrastructure partners to sustain the Godot Agentic Ecosystem. Every contribution helps us maintain these skills and keep them free for the community.

🚀 View our Sponsorship & Support Opportunities

Get in Touch: [email protected]

---

📜 License

This project is licensed under the GNU Lesser General Public License v3.0 - see LICENSE for details.

Why LGPLv3?
We chose this license because it strikes the perfect balance for an open ecosystem. It ensures that any improvements or additions made directly to the GDSkills library itself remain open-source and shared with the community. At the same time, it empowers you to use these agentic skills to build and compile your own incredible games, which you are completely free to commercialize and keep closed-source if you wish.

By contributing, you agree that your code will be licensed under the project’s LGPLv3 License.

---