summer-engine 1.2.0 → 1.3.0

package/skills/{scene-composition → scene-and-project/scene-composition}/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: scene-composition
-description: How to structure scenes, when to use sub-scenes, and node hierarchy conventions. Use when building scenes, organizing nodes, or creating reusable prefabs.
+description: How to structure scenes, when to use sub-scenes, node hierarchy conventions, and reusable prefabs. Use when building scenes, organizing nodes, or creating instanced prefabs. Trigger on "scene", "sub-scene", "instance", "prefab", "node hierarchy".
 license: MIT
-compatibility:
-  - Cursor
-  - Claude Code
-  - Windsurf
+compatibility: [Cursor, Claude Code, Windsurf, Codex]
+category: scene-and-project
+allowed-tools: Read Grep summer_create_scene summer_open_scene summer_get_scene_tree summer_add_node summer_instantiate_scene summer_save_scene
+paths: ["**/*.tscn"]
 ---
 
 # Scene Composition for Summer Engine
@@ -79,7 +79,7 @@ Use `./` for paths relative to the scene root:
 
 1. Build the hierarchy in the main scene
 2. Select the root of what you want to extract
-3. Save as scene: `summer_save_scene(path="res://scenes/player.tscn")` — but note: SaveScene saves the *current* scene. To save a branch, you typically save the open scene first, then in the editor you'd use "Save Branch as Scene." MCP doesn't have a direct "save branch" op—so for now, create the sub-scene as its own file via `summer_write_file` or build it in a separate scene and save.
+3. Save as scene: `summer_save_scene(path="res://scenes/player.tscn")`. SaveScene saves the current open scene, so build reusable scenes in their own open scene and save them there. Do not handwrite `.tscn` files as the preferred path.
 4. In the main scene, add it with `summer_instantiate_scene(parent="./World", scene="res://scenes/player.tscn", name="Player")`
 
 **Practical approach:** Create reusable scenes (player.tscn, enemy.tscn) as separate scene files, then instantiate them into levels.

package/skills/{gdscript-patterns → scripting-patterns/gdscript-patterns}/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: gdscript-patterns
-description: Common GDScript idioms, signals, exports, and type hints. Use when writing GDScript, attaching scripts to nodes, connecting signals, or defining exported variables.
+description: Common GDScript idioms — type hints, signals, exports, onready, lifecycle methods, naming conventions. Use when writing GDScript, attaching scripts, or refactoring untyped code. Trigger on "GDScript", "script", "signals", "exports".
 license: MIT
-compatibility:
-  - Cursor
-  - Claude Code
-  - Windsurf
+compatibility: [Cursor, Claude Code, Windsurf, Codex]
+category: scripting-patterns
+allowed-tools: Read Grep summer_get_script_errors
+paths: ["**/*.gd"]
 ---
 
 # GDScript Patterns for Summer Engine
@@ -89,8 +89,8 @@ var siblings = get_parent().get_children()
 
 For health systems, input handling, and state machines, see [reference.md](reference.md).
 
-## MCP Integration
+## Scene Integration
 
-When the AI adds a script via `summer_add_node` and attaches a script, the script path is set via `summer_set_prop(path, "script", "res://path/to/script.gd")`. The script file must exist—use `summer_write_file` to create it first.
+When the AI adds a node with Summer MCP tools and attaches a script, the script path is set via `summer_set_prop(path, "script", "res://path/to/script.gd")`. The script file must exist first. Create or edit `.gd` files with the host agent's normal file-editing tools, then use Summer MCP only to attach the script and connect scene signals.
 
 For signal connections, the receiver must have the handler method. Create the script with the method stub before calling `summer_connect_signal`.

package/skills/{ui-basics → ui-and-ux/ui-basics}/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: ui-basics
-description: HUD, menus, health bars, and responsive UI layout. Use when building menus, HUDs, health bars, or Control-based UI in Summer Engine.
+description: HUD, menus, health bars, progress bars, and Control-based UI layout. Use when building menus, HUDs, health bars, or any Control-tree UI. Trigger on "UI", "HUD", "menu", "health bar", "Control".
 license: MIT
-compatibility:
-  - Cursor
-  - Claude Code
-  - Windsurf
+compatibility: [Cursor, Claude Code, Windsurf, Codex]
+category: ui-and-ux
+allowed-tools: Read Grep summer_add_node summer_set_prop summer_connect_signal summer_save_scene
+paths: ["**/*.tscn", "**/*.gd"]
 ---
 
 # UI Basics for Summer Engine