godot-live-edit
Skill35 starsChanged 10 months agoMITView on GitHub
You are an expert at using the Godot AI Bridge to control a running Godot editor in real-time. This skill guides you through live editing workflows. When modifying properties via live editing, use these JSON formats:
In this repository4 other files it gives its agents.
- godot-code-genSkill
- godot-interactiveSkill
- godot-scene-designSkill
- godot-shaderSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 99
When modifying properties via live editing, use these JSON formats:
- Distinctive: line 180
Work incrementally: - Add one node, verify, then continue
- Very specific: line 182
Check the scene tree: - Use godot_editor_get_scene_tree to verify structure
- Very specific: line 183
Inspect before modifying: - Use godot_editor_get_node_properties to see current values
- Distinctive: line 184
Use undo if needed: - All operations support Ctrl+Z in the editor
- Very specific: line 185
Refresh filesystem: - After external file changes, use godot_editor_refresh_filesystem
- Very specific: line 201
Use godot_editor_get_node_types to list all instantiable node types:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Godot Live Edit Skill
You are an expert at using the Godot AI Bridge to control a running Godot editor in real-time. This skill guides you through live editing workflows.
Connection Workflow
Step 1: Connect to Godot
First, ensure:
1. Godot 4.x is running with your project open
2. The godot-ai-bridge plugin is installed and enabled
3. The plugin shows "AI Bridge listening on port 6550" in output
Then use: godot_connectStep 2: Verify Connection
Use: godot_connection_status
Expected response:
{
"connected": true,
"port": 6550,
"projectPath": "/path/to/project"
}Step 3: Explore the Scene
Use: godot_editor_get_scene_tree
This shows all nodes in the current scene with their types and hierarchy.Common Live Edit Operations
Adding UI Elements
To add a health bar:
1. godot_editor_add_node
- parent: "HUD" (or ".")
- name: "HealthBar"
- type: "ProgressBar"
- properties: { "value": 100, "max_value": 100 }
2. godot_editor_modify_node
- nodePath: "HUD/HealthBar"
- properties: {
"position": {"_type": "Vector2", "x": 20, "y": 20},
"size": {"_type": "Vector2", "x": 200, "y": 30}
}Modifying Node Properties
To reposition a player:
godot_editor_modify_node
- nodePath: "Player"
- properties: {
"position": {"_type": "Vector2", "x": 100, "y": 200},
"scale": {"_type": "Vector2", "x": 2, "y": 2}
}Inspecting Nodes
To see all properties of a node:
godot_editor_get_node_properties
- nodePath: "Player"
- filter: "exported" (or "all" for everything)Building Scene Hierarchies
To create a character scene structure:
1. Root: godot_editor_add_node (type: CharacterBody2D, name: Player)
2. Sprite: godot_editor_add_node (parent: Player, type: Sprite2D)
3. Collision: godot_editor_add_node (parent: Player, type: CollisionShape2D)
4. Camera: godot_editor_add_node (parent: Player, type: Camera2D)Running and Testing
Test your changes:
1. godot_editor_save_scene - Save current work
2. godot_editor_run_scene - Run and test
3. godot_editor_stop_scene - Stop when done
4. godot_editor_get_errors - Check for issuesProperty Type Formatting
When modifying properties via live editing, use these JSON formats:
Vector2
{
"_type": "Vector2",
"x": 100.0,
"y": 200.0
}Vector3
{
"_type": "Vector3",
"x": 1.0,
"y": 2.0,
"z": 3.0
}Color
{
"_type": "Color",
"r": 1.0,
"g": 0.5,
"b": 0.0,
"a": 1.0
}Simple Values
{
"visible": true,
"rotation": 1.57,
"speed": 200.0,
"text": "Hello World"
}Workflow Patterns
Iterative UI Design
1. Connect to editor
2. Get current scene tree
3. Add container nodes (VBoxContainer, HBoxContainer)
4. Add UI elements (Label, Button, ProgressBar)
5. Adjust positions/sizes with modify_node
6. Run scene to preview
7. Iterate until satisfied
8. Save sceneLevel Building
1. Connect to editor
2. Instantiate pre-made scenes (enemies, items, platforms)
3. Position them with modify_node
4. Duplicate nodes as needed
5. Run to test gameplay
6. Adjust and iterateDebugging
1. Connect to editor
2. Run scene
3. Use get_errors to check for problems
4. Execute GDScript to inspect runtime state:
godot_editor_execute_gdscript
- code: "return get_tree().current_scene.get_node('Player').position"
5. Stop scene
6. Fix issuesBest Practices
- Always save before running -
godot_editor_save_scenefirst - Work incrementally - Add one node, verify, then continue
- Use descriptive names - "PlayerHealthBar" not "ProgressBar2"
- Check the scene tree - Use
godot_editor_get_scene_treeto verify structure - Inspect before modifying - Use
godot_editor_get_node_propertiesto see current values - Use undo if needed - All operations support Ctrl+Z in the editor
- Refresh filesystem - After external file changes, use
godot_editor_refresh_filesystem
Error Handling
Common issues:
| Error | Cause | Solution |
| "Not connected" | Plugin not running | Start Godot, enable plugin |
| "Node not found" | Wrong path | Use get_scene_tree to find correct path |
| "No scene open" | No scene loaded | Open a scene in Godot first |
| "Parent not found" | Invalid parent path | Check parent exists in tree |
| "Failed to create node" | Invalid node type | Verify type name (case-sensitive) |
Available Node Types
Use godot_editor_get_node_types to list all instantiable node types:
godot_editor_get_node_types
- base_type: "Control" // List all UI nodes
- base_type: "Node2D" // List all 2D nodes
- base_type: "Node3D" // List all 3D nodesScene Management
# List all scenes in project
godot_editor_list_assets_by_type
- type: "scenes"
# Open a different scene
godot_editor_open_scene
- scenePath: "res://scenes/main_menu.tscn"
# Save as new scene
godot_editor_save_scene_as
- path: "res://scenes/level_2.tscn"
# Instantiate a scene as child
godot_editor_instantiate_scene
- scene_path: "res://scenes/enemy.tscn"
- parent: "Enemies"
- name: "Enemy1"Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

