New Scene

If the type is ambiguous, ask the user.

Step 2 — Look Up Documentation (MANDATORY — do not skip)

You MUST complete ALL of these before writing any code:

1. Call the godot-docs skill for the root node type and key child types:

   activate_skill("godot-docs") # Look up [ROOT_NODE_TYPE] and [CHILD_TYPES]. I need properties, methods, signals, and code examples for creating a [SCENE_TYPE] scene.
   

2. Read the scene architecture best practices:

   Read("docsbest-practices/01-scene-architecture.md")
   

3. If this scene has signals, also read docsbest-practices/02-signals-and-communication.md

Step 3 — Create Directory Structure

Ensure the target directory exists under gamescenes/.

Step 4 — Create the Scene (.tscn)

Create a .tscn file with the proper Godot scene format. Use [gd_scene] header, [ext_resource] for external assets, [sub_resource] for inline resources, and [node] entries.

Scene File Template

[gd_scene load_steps=2 format=3]

[ext_resource type="Script" path="res:/scenes/<category>/<name>.gd" id="1"]

[node name="<RootName>" type="<RootType>"]
script = ExtResource("1")

[node name="<ChildName>" type="<ChildType>" parent="."]

Step 5 — Create the Script (.gd)

Generate a GDScript file following these conventions from gemini.md:

Script Template

class_name <PascalCaseName>
extends <RootNodeType>
## <Brief description of what this sceneentity does.>


signal <relevant_signal>


enum <RelevantEnum> {
	VALUE_ONE,
	VALUE_TWO,
}


const <RELEVANT_CONSTANT>: <type> = <value>


@export var <exported_property>: <type> = <default>


var <internal_property>: <type> = <default>


@onready var <child_ref>: <Type> = $<ChildNodeName>


func _ready() -> void:
	pass


func _physics_process(delta: float) -> void:
	pass

Code Style Rules (from gemini.md)

• Use tabs for indentation
• Use static typing everywhere
• Use double quotes for strings
• Use @export for inspector-exposed variables
• Use @onready for child node references
• Use and/or/not over &&/||/!
• Trailing commas in multiline arrays, dicts, enums
• Two blank lines between functions
• Lines under 100 characters (prefer 80)
• Signals in past tense (e.g., health_changed, died)
• Private members prefixed with _

Step 6 — Report

After creating files, report:

1. Files created (with full paths)
2. Node hierarchy of the scene
3. Signals and exports defined
4. Suggested next steps (e.g., "Add sprite frames", "Set collision shape", "Connect signals")