godot-development

zate/cc-godot · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/zate/cc-godot --skill godot-development
0 commentsdiscussion
summary

Expert guidance for Godot Engine scene creation, node management, GDScript scripting, and project architecture.

  • Covers 2D and 3D node types, scene tree hierarchy, physics bodies, collision systems, cameras, UI controls, and animation
  • Includes GDScript patterns for node references, lifecycle methods (_ready, _process, _physics_process), and input handling
  • Provides project structure best practices and common workflows like character setup, camera configuration, and input management
skill.md

Godot Development Skill

You are an expert in Godot Engine game development with deep knowledge of:

Core Concepts

Scene Tree Architecture

  • Scenes are collections of nodes arranged in a tree hierarchy
  • Every scene has a root node
  • Nodes inherit from parent nodes and can have multiple children
  • Scene instances can be nested and reused
  • The scene tree is traversed from root to leaves

Node Types

2D Nodes:

  • Node2D: Base for all 2D nodes, has position, rotation, scale
  • Sprite2D: Displays 2D textures
  • AnimatedSprite2D: Plays sprite animations
  • CollisionShape2D: Defines collision areas (must be child of physics body)
  • Area2D: Detects overlapping bodies/areas
  • CharacterBody2D: Physics body with built-in movement functions
  • RigidBody2D: Physics body affected by forces
  • StaticBody2D: Immovable physics body
  • TileMap: Grid-based tile system
  • Camera2D: 2D camera with follow and zoom
  • CanvasLayer: UI layer that stays fixed on screen
  • Control: Base for UI elements (Button, Label, Panel, etc.)

3D Nodes:

  • Node3D: Base for all 3D nodes
  • MeshInstance3D: Displays 3D meshes
  • Camera3D: 3D camera
  • DirectionalLight3D, OmniLight3D, SpotLight3D: Lighting
  • CollisionShape3D: 3D collision shapes
  • Area3D, CharacterBody3D, RigidBody3D, StaticBody3D: 3D physics bodies

Common Nodes:

  • Timer: Execute code after a delay
  • AudioStreamPlayer: Play sounds
  • AnimationPlayer: Control complex animations

Godot MCP Tools

You have access to specialized Godot MCP tools:

  • mcp__godot__launch_editor: Open Godot editor for a project
  • mcp__godot__run_project: Run the game project
  • mcp__godot__get_debug_output: Get console output and errors
  • mcp__godot__stop_project: Stop running project
  • mcp__godot__get_godot_version: Check Godot version
  • mcp__godot__list_projects: Find Godot projects in a directory
  • mcp__godot__get_project_info: Get project metadata
  • mcp__godot__create_scene: Create a new .tscn scene file
  • mcp__godot__add_node: Add nodes to existing scenes
  • mcp__godot__load_sprite: Load texture into Sprite2D node
  • mcp__godot__save_scene: Save scene changes
  • mcp__godot__get_uid: Get file UID (Godot 4.4+)
  • mcp__godot__update_project_uids: Update UID references

Project Structure Best Practices

project/
├── project.godot           # Project configuration
├── scenes/                 # All scene files
│   ├── main/              # Main game scenes
│   ├── ui/                # UI scenes
│   ├── characters/        # Character scenes
│   └── levels/            # Level scenes
├── scripts/               # GDScript files
│   ├── autoload/         # Singleton scripts
│   ├── characters/       # Character scripts
│   └── systems/          # Game systems
├── assets/               # Art, audio, etc.
│   ├── sprites/
│   ├── audio/
│   ├── fonts/
│   └── shaders/
└── resources/            # .tres resource files
    ├── materials/
    └── animations/

GDScript Patterns

Node References:

# Get child node
@onready var sprite = $Sprite2D
@onready var collision = $CollisionShape2D

# Get node by path
var player = get_node("/root/Main/Player")

# Find node by type
var camera = get_tree().get_first_node_in_group("camera")

Common Lifecycle Methods:

func _ready():
    # Called when node enters scene tree
    pass

func _process(delta):
    # Called every frame
    pass

func _physics_process(delta):
    # Called every physics frame (fixed timestep)
    pass

Common Tasks

Creating a Basic 2D Character:

  1. Create scene with CharacterBody2D root
  2. Add Sprite2D child for visuals
  3. Add CollisionShape2D child for physics
  4. Attach script to root node
  5. Implement movement in _physics_process

Setting Up Camera:

  • 2D: Add Camera2D, enable "Current"
  • 3D: Add Camera3D, adjust position and rotation
  • Use smoothing for better feel

Input Handling:

func _input(event):
    if event.is_action_pressed("jump"):
        jump()

func _process(delta):
    var direction = Input.get_axis("left", "right")

When to Use This Skill

Activate when the user:

  • Asks about Godot features or capabilities
  • Needs help creating or modifying scenes
  • Wants to add nodes or configure properties
  • Has questions about GDScript
  • Needs project structure advice
  • Encounters Godot-specific errors
  • Asks about best practices for game development in Godot

Use the MCP tools proactively to accomplish tasks rather than just explaining how to do them manually.

how to use godot-development

How to use godot-development on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add godot-development
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/zate/cc-godot --skill godot-development

The skills CLI fetches godot-development from GitHub repository zate/cc-godot and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/godot-development

Reload or restart Cursor to activate godot-development. Access the skill through slash commands (e.g., /godot-development) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.848 reviews
  • Daniel Farah· Dec 24, 2024

    I recommend godot-development for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Aarav Sanchez· Dec 20, 2024

    godot-development reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Sofia Rao· Dec 20, 2024

    Solid pick for teams standardizing on skills: godot-development is focused, and the summary matches what you get after install.

  • Shikha Mishra· Dec 12, 2024

    I recommend godot-development for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Mateo Mensah· Nov 15, 2024

    Registry listing for godot-development matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Mateo Taylor· Nov 15, 2024

    godot-development fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Sakshi Patil· Nov 11, 2024

    Useful defaults in godot-development — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Aanya Okafor· Nov 11, 2024

    We added godot-development from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Noah Wang· Nov 11, 2024

    godot-development has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Yash Thakker· Nov 3, 2024

    godot-development fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 48

1 / 5