summer-engine 1.2.0 → 1.3.0

package/skills/_tests/specs/fps-controller.md

@@ -0,0 +1,100 @@
+# Skill Spec: /fps-controller
+
+## Fixture
+
+- Empty Godot 4.5 / Summer Engine project, main scene open with a single `World` (Node3D) root.
+- Summer MCP tools available (engine running on localhost:6550).
+- No existing input actions in InputMap beyond Godot defaults.
+- No script files attached.
+
+## Case 1: Happy Path — fresh FPS in an empty scene
+
+**Input:** "Add a first-person controller to my scene."
+
+**Expected MCP tool sequence (in order):**
+
+1. `summer_get_scene_tree` — verify empty World exists.
+2. `summer_add_node(parent="./World", type="CharacterBody3D", name="Player")`
+3. `summer_add_node(parent="./World/Player", type="CollisionShape3D", name="Collision")`
+4. `summer_add_node(parent="./World/Player", type="Camera3D", name="Camera")`
+5. `summer_set_prop("./World/Player/Collision", "shape", "CapsuleShape3D")` (creates standalone, NOT inline sub-resource)
+6. `summer_set_resource_property("./World/Player/Collision", "shape.height", "1.8")` (only after the shape is standalone)
+7. `summer_set_prop("./World/Player/Camera", "position", "Vector3(0, 1.6, 0)")`
+8. `summer_input_map_bind("move_forward", "key:W")`
+9. `summer_input_map_bind("move_back", "key:S")`
+10. `summer_input_map_bind("move_left", "key:A")`
+11. `summer_input_map_bind("move_right", "key:D")`
+12. `summer_input_map_bind("jump", "key:Space")`
+13. (User-side write) `Write` script file `scripts/player_controller.gd` after the agent asks "May I attach the controller script to ./World/Player?"
+14. `summer_save_scene`
+15. `summer_get_script_errors`
+
+**Assertions:**
+
+- [ ] CharacterBody3D node exists at `./World/Player`.
+- [ ] CollisionShape3D is a child of Player with a CapsuleShape3D (NOT BoxShape, NOT SphereShape).
+- [ ] Camera3D positioned at `y ≈ 1.6` (head height).
+- [ ] All 5 input actions bound: `move_forward`, `move_back`, `move_left`, `move_right`, `jump`.
+- [ ] Skill asks "May I create / attach …" before the script write.
+- [ ] Skill never calls `summer_set_resource_property` on an inline `sub_resource` (the silent-fail trap from `_shared/mcp-tools-reference.md`).
+- [ ] Final step is `summer_save_scene` followed by `summer_get_script_errors`.
+- [ ] Script uses typed GDScript per `_shared/gd-style.md` (`@export`, `:=`, `class_name`).
+
+## Case 2: Failure Path — existing PlayerOld in scene
+
+**Fixture:** Same as Case 1, but `World/PlayerOld` exists with a CharacterBody3D + collision (manually authored).
+
+**Input:** "Add a first-person controller to my scene."
+
+**Expected behavior:**
+
+- Skill detects the name collision via `summer_get_scene_tree`.
+- Skill asks: "I see `World/PlayerOld` already exists. Should I replace it, add a second player as `Player2`, or something else?"
+- Does NOT silently overwrite.
+
+**Assertions:**
+
+- [ ] Skill calls `summer_get_scene_tree` before any mutation.
+- [ ] Skill asks the user how to handle the collision before adding any node.
+- [ ] No `summer_add_node` calls happen until the user answers.
+
+## Case 3: Edge Case — user says "third-person"
+
+**Fixture:** Empty Godot project, main scene with `World` only.
+
+**Input:** "Build a third-person FPS controller."
+
+**Expected behavior:**
+
+- Skill clarifies the contradiction: FPS = first-person; third-person ≠ FPS.
+- Either asks the user which they meant, OR hands off to `/tps-controller` (when that skill ships) and explains the difference.
+
+**Assertions:**
+
+- [ ] Skill does NOT silently start building a third-person controller using FPS scaffolding.
+- [ ] Skill explicitly names the ambiguity ("FPS means first-person; third-person is a separate skill").
+- [ ] Skill offers a clear next step: clarify or use the right skill.
+
+## Case 4: No Summer MCP — file-edit fallback path
+
+**Fixture:** Same as Case 1 except Summer MCP is NOT available (running in plain Cursor on a project where the engine is not connected).
+
+**Input:** "Add a first-person controller to my scene."
+
+**Expected behavior:**
+
+- Skill detects no MCP and falls back to direct file edits on `level.tscn`.
+- Writes a `.tscn` snippet with CharacterBody3D + CollisionShape3D + Camera3D following the format in the skill's "Fallback (no MCP)" sections.
+- Writes `scripts/player_controller.gd` directly via host file-write tools.
+- Edits `project.godot` to add the InputMap actions.
+
+**Assertions:**
+
+- [ ] Skill identifies that MCP is unavailable (does not blindly call `summer_*` tools and fail).
+- [ ] Generated `.tscn` is syntactically valid Godot 4 scene format (parseable by Godot).
+- [ ] Generated `project.godot` patch follows Godot's input action format (`input/move_forward = { ... }`).
+- [ ] Skill still asks "May I write …" before each file write.
+
+---
+
+This spec runs via `/skill-test fps-controller spec` (see `_meta/skill-test/SKILL.md`).

package/skills/_tests/specs/gdscript-patterns.md

@@ -0,0 +1,19 @@
+# Skill Spec: /gdscript-patterns
+
+> Stub spec. Expand with Happy / Failure / Edge cases. See `fps-controller.md` for the canonical format.
+
+## Fixture
+
+- TBD
+
+## Case 1: Happy Path
+
+**Input:** "<typical user prompt>"
+
+**Expected MCP tool sequence (in order):**
+
+1. TBD
+
+**Assertions:**
+
+- [ ] TBD

package/skills/_tests/specs/make-game.md

@@ -0,0 +1,19 @@
+# Skill Spec: /make-game
+
+> Stub spec. Expand with Happy / Failure / Edge cases. See `fps-controller.md` for the canonical format.
+
+## Fixture
+
+- TBD
+
+## Case 1: Happy Path
+
+**Input:** "<typical user prompt>"
+
+**Expected MCP tool sequence (in order):**
+
+1. TBD
+
+**Assertions:**
+
+- [ ] TBD

package/skills/_tests/specs/scene-composition.md

@@ -0,0 +1,19 @@
+# Skill Spec: /scene-composition
+
+> Stub spec. Expand with Happy / Failure / Edge cases. See `fps-controller.md` for the canonical format.
+
+## Fixture
+
+- TBD
+
+## Case 1: Happy Path
+
+**Input:** "<typical user prompt>"
+
+**Expected MCP tool sequence (in order):**
+
+1. TBD
+
+**Assertions:**
+
+- [ ] TBD

package/skills/_tests/specs/ui-basics.md

@@ -0,0 +1,19 @@
+# Skill Spec: /ui-basics
+
+> Stub spec. Expand with Happy / Failure / Edge cases. See `fps-controller.md` for the canonical format.
+
+## Fixture
+
+- TBD
+
+## Case 1: Happy Path
+
+**Input:** "<typical user prompt>"
+
+**Expected MCP tool sequence (in order):**
+
+1. TBD
+
+**Assertions:**
+
+- [ ] TBD

package/skills/{asset-strategy → asset-pipeline/asset-strategy}/SKILL.md

@@ -1,11 +1,10 @@
 ---
 name: asset-strategy
-description: Decision guide for how to create different game asset types. Use when deciding whether to generate 3D models, textures, or use primitives. Includes prompt templates for AI image-to-3D pipeline.
+description: Decision guide for how to create different game asset types — generated 3D, library search, AI textures, or primitives. Use when planning asset creation, picking an asset pipeline, or writing image-to-3D prompts. Trigger on "assets", "3D models", "textures", "art pipeline".
 license: MIT
-compatibility:
-  - Cursor
-  - Claude Code
-  - Windsurf
+compatibility: [Cursor, Claude Code, Windsurf, Codex]
+category: asset-pipeline
+allowed-tools: Read Grep summer_search_assets summer_import_asset summer_generate_image summer_generate_3d summer_generate_audio summer_import_from_url
 ---
 
 # Asset Strategy for Summer Engine