summer-engine 1.3.1 → 1.3.2

package/skills/_tests/specs/design-mechanic.md

@@ -0,0 +1,112 @@
+# Skill Spec: /design-mechanic
+
+## Fixture
+
+- Godot 4.5 / Summer Engine project with `World/Player` (CharacterBody3D + CollisionShape3D + Camera3D) already in the main scene.
+- A `scripts/player_controller.gd` exists with single-jump logic.
+- `.summer/GameSoul.md` exists, brief says: "core loop is precise platforming, three mechanics: dash, double-jump, parry".
+- Summer MCP available.
+
+## Case 1: Happy Path — design double-jump
+
+**Input:** "Design the double-jump mechanic."
+
+**Expected MCP tool sequence (in order):**
+
+1. (Skill asks one clarifying question if any — e.g., "Tap or hold-and-release?" — and waits.)
+2. `Read .summer/GameSoul.md` — anchor to the brief
+3. (Skill walks the five layers: input, response, feedback (visual/audio/mechanical), failure modes, depth)
+4. (Skill names tunables as `@export` vars)
+5. (Skill sketches the node-graph plan and asks "May I add `DoubleJumpFX` and `JumpAudio` to `./World/Player`?")
+6. `summer_get_scene_tree` — confirm Player exists
+7. `summer_add_node(parent="./World/Player", type="GPUParticles3D", name="DoubleJumpFX")`
+8. `summer_set_prop("./World/Player/DoubleJumpFX", "emitting", "false")`
+9. `summer_add_node(parent="./World/Player", type="AudioStreamPlayer3D", name="JumpAudio")`
+10. `summer_input_map_bind(name="jump", events=[{type:"key", key:"Space"}])` (idempotent)
+11. (Skill asks "May I modify `scripts/player_controller.gd` to add double-jump logic?")
+12. `Edit scripts/player_controller.gd` — merge double-jump logic
+13. (Skill asks "May I create `.summer/mechanics/double-jump.md` with the design doc?")
+14. `Write .summer/mechanics/double-jump.md`
+15. `summer_save_scene`
+16. `summer_get_script_errors`
+
+**Assertions:**
+
+- [ ] Skill reads `.summer/GameSoul.md` to anchor the design to the brief.
+- [ ] Skill walks all five layers (input, response, feedback, failure modes, depth) before scaffolding.
+- [ ] Skill enforces all THREE feedback channels (visual, audio, mechanical) — pushes back if user only names two.
+- [ ] Skill lists 3-7 tunables as `@export` vars (not `const`).
+- [ ] Skill asks "May I add ..." before scene mutations.
+- [ ] Skill asks "May I modify ..." before script edits.
+- [ ] Skill writes the design doc to `.summer/mechanics/<name>.md`.
+- [ ] Skill never calls `summer_set_resource_property` on an inline sub_resource (silent-fail trap).
+- [ ] Generated GDScript uses typed vars, `@export`, `class_name`, `@onready`, signals (matches `_shared/gd-style.md`).
+- [ ] Final step is `summer_save_scene` then `summer_get_script_errors`.
+
+## Case 2: Failure Path — user names a system, not a mechanic
+
+**Fixture:** Same as Case 1.
+
+**Input:** "Design the inventory."
+
+**Expected behavior:**
+
+- Skill recognizes "inventory" is a system, not a mechanic.
+- Skill pushes back: "Inventory is a system. The mechanics inside it are pickup, equip, drop, use, swap. Which one?"
+- Does NOT start designing a generic "inventory mechanic".
+- Waits for the user to pick a verb.
+
+**Assertions:**
+
+- [ ] Skill explicitly distinguishes system vs. mechanic.
+- [ ] Skill asks the user to pick a verb before walking the five layers.
+- [ ] No scene mutations or file writes happen until the user picks.
+
+## Case 3: Edge Case — user can't articulate depth
+
+**Fixture:** Same as Case 1.
+
+**Input:** "Design the double-jump."
+
+**During step 3, on Layer 5 (depth):**
+
+User says: "Players will use it strategically."
+
+**Expected behavior:**
+
+- Skill rejects the hand-wave: "That's not depth — name the choice the player makes."
+- Skill offers a concrete frame: "Depth = the resource is finite or has a cost, and level design forces a choice between using it now or saving it. If neither is true, this is just a higher-jumping single-jump."
+- Skill asks the user to either (a) name the cost / choice, or (b) cut the mechanic.
+- Skill does NOT scaffold a depth-less mechanic.
+
+**Assertions:**
+
+- [ ] Skill does not accept "strategically" / "for skilled play" / "it's interesting" as depth.
+- [ ] Skill names a concrete depth-vector (cost, resource, choice).
+- [ ] Skill explicitly offers "cut the mechanic" as a valid outcome.
+- [ ] No scaffolding happens until depth is articulated.
+
+## Case 4: No Summer MCP — file-edit fallback
+
+**Fixture:** Same as Case 1, but Summer MCP is unavailable (engine not connected).
+
+**Input:** "Design the double-jump mechanic."
+
+**Expected behavior:**
+
+- Skill detects no MCP and falls back to file edits.
+- Walks the five layers normally.
+- Instead of `summer_add_node`, prints the `.tscn` snippet for `DoubleJumpFX` and `JumpAudio` nodes for the user to paste into the scene file (or asks the user which `.tscn` to edit).
+- Asks before each file write.
+- Still writes the GDScript stub via `Edit` and the design doc via `Write`.
+
+**Assertions:**
+
+- [ ] Skill identifies that MCP is unavailable; does not blindly call `summer_*` tools.
+- [ ] Generated `.tscn` snippet is syntactically valid Godot 4 scene format.
+- [ ] Skill still asks "May I write ..." before each file write.
+- [ ] Skill still produces both the GDScript stub AND the design doc at `.summer/mechanics/<name>.md`.
+
+---
+
+This spec runs via `/skill-test design-mechanic spec` (see `_meta/skill-test/SKILL.md`).

package/skills/_tests/specs/design-npc.md

@@ -0,0 +1,112 @@
+# Skill Spec: /design-npc
+
+## Fixture
+
+- Godot 4.5 / Summer Engine project, main scene with `World/Player` (CharacterBody3D in `player` group) and an empty `World/Enemies` parent.
+- Summer MCP tools available.
+- Host file tools available (Read, Edit, Write).
+
+## Case 1: Happy Path — basic patrol-and-chase enemy
+
+**Input:** "Add a basic enemy that chases the player when it sees them."
+
+**Expected MCP tool sequence (in order):**
+
+1. (Skill asks the archetype question and waits.)
+2. User confirms "basic enemy".
+3. `summer_get_scene_tree`
+4. `summer_inspect_node "./World/Player"` — confirms it's in `player` group
+5. (Skill proposes the bundle: scene tree + script + states + telegraph + loot hook + "May I create?")
+6. After user OK:
+   - `summer_add_node(parent="./World/Enemies", type="CharacterBody3D", name="Enemy")`
+   - `summer_add_node(parent="./World/Enemies/Enemy", type="CollisionShape3D", name="Body")`
+   - `summer_add_node(parent="./World/Enemies/Enemy", type="MeshInstance3D", name="Mesh")`
+   - `summer_add_node(parent="./World/Enemies/Enemy", type="Area3D", name="Vision")`
+   - `summer_add_node(parent="./World/Enemies/Enemy/Vision", type="CollisionShape3D", name="VisionShape")`
+   - `summer_add_node(parent="./World/Enemies/Enemy", type="RayCast3D", name="Sight")`
+   - (Vision SphereShape3D saved as standalone `.tres`, NOT inline)
+   - `summer_set_prop` on Sight: `enabled = true`
+   - `Write scripts/enemy_ai.gd`
+   - `summer_connect_signal(from="./World/Enemies/Enemy/Vision", signal="body_entered", to="./World/Enemies/Enemy", method="_on_body_entered")`
+   - `summer_save_scene`
+   - `summer_get_script_errors`
+
+**Assertions:**
+
+- [ ] Skill asks the archetype question before any tool call.
+- [ ] Scene has BOTH a Vision Area3D AND a Sight RayCast3D (the two-step perception pattern).
+- [ ] Vision shape is saved as a standalone `.tres`, NOT inline sub_resource (silent-fail trap).
+- [ ] Script defines an `enum State` with at least 4 states (idle / alert / attack / dead).
+- [ ] Script has an attack `telegraph` parameter in 0.3–0.7 sec range.
+- [ ] Script emits a `died` signal.
+- [ ] Script uses `distance_squared_to` (NOT `distance_to`) for range comparisons.
+- [ ] Script uses typed GDScript per `_shared/gd-style.md`.
+- [ ] Skill asks "May I create / write …" before each user-visible mutation.
+- [ ] Final step is `summer_save_scene` then `summer_get_script_errors`.
+
+## Case 2: Failure Path — wave-mob archetype but user asks for full FSM
+
+**Fixture:** User wants 100+ enemies on screen at once.
+
+**Input:** "Spawn 100 enemies that chase the player. Each one should perceive, decide, telegraph attacks, and drop loot."
+
+**Expected behavior:**
+
+- Skill recognizes the scale conflict.
+- Says: "100 enemies with full FSM + LOS perception will eat your frame budget. For wave mobs at this scale, the right archetype is the wave-mob (2 states, no LOS, direct line to player). Want me to build that instead?"
+- Does NOT silently build 100 expensive enemies.
+- Offers the trade-off explicitly.
+
+**Assertions:**
+
+- [ ] Skill names the performance trade-off, not just "this is hard".
+- [ ] Skill points to the wave-mob archetype as the right answer.
+- [ ] Skill does NOT proceed without confirmation.
+- [ ] Skill never starts spawning 100 expensive nodes.
+
+## Case 3: Edge Case — boss with phases
+
+**Fixture:** Same as Case 1.
+
+**Input:** "Design a 3-phase boss for the dungeon room."
+
+**Expected behavior:**
+
+- Skill picks the **boss** archetype (different complexity budget).
+- Calls out: "Boss complexity (6–10 states, scripted phases) is at the threshold where a behavior tree might pay off, but I recommend a hand-coded FSM with phase enum first since you're a single dev."
+- Walks the four pillars but at boss scale: more tells per state, telegraph 0.5–0.7 sec, distinct mechanics per phase (cap at 4–6 total mechanics).
+- Defers to `ai-and-npcs/boss-patterns/SKILL.md` for the deeper phase-transition patterns.
+- Does NOT just scale up the basic-enemy stub.
+
+**Assertions:**
+
+- [ ] Skill recognizes "boss" requires a different design.
+- [ ] Skill caps at 4–6 distinct mechanics across phases.
+- [ ] Skill mentions phase enum as the FSM extension.
+- [ ] Skill defers to boss-patterns for deeper detail rather than trying to one-shot it.
+
+## Case 4: No Summer MCP — fallback path
+
+**Fixture:** Same as Case 1, but Summer MCP unavailable.
+
+**Input:** "Add a basic enemy that chases the player."
+
+**Expected behavior:**
+
+- Skill detects MCP unavailable.
+- Asks user to paste the existing scene tree (or the relevant `.tscn` snippet) so node paths are right.
+- Generates a `.tscn` snippet (Enemy + Vision + Sight + Mesh + CollisionShape) with valid Godot 4 scene syntax.
+- Writes `scripts/enemy_ai.gd` directly.
+- Provides manual editor instructions for connecting the `body_entered` signal (or a connection block in the `.tscn`).
+- Still asks "May I write …" before each file write.
+
+**Assertions:**
+
+- [ ] Skill does not blindly call `summer_*` tools and fail.
+- [ ] Generated `.tscn` is valid Godot 4 syntax (parseable).
+- [ ] Generated GDScript has the same FSM structure (states / telegraph / died signal).
+- [ ] Skill still asks "May I" on writes.
+
+---
+
+This spec runs via `/skill-test design-npc spec` (see `_meta/skill-test/SKILL.md`).

package/skills/_tests/specs/export-and-ship.md

@@ -0,0 +1,114 @@
+# Skill Spec: /export-and-ship
+
+## Fixture
+
+- Godot 4.5 / Summer Engine project, complete game with main scene set, no script errors, basic icon at `icon.png` (256×256).
+- Existing `export_presets.cfg` with Windows/Mac/Linux presets, all `debug = true` (development defaults).
+- No `LICENSE` file at repo root.
+- No `attribution.md`.
+- Two CC-BY 4.0 assets imported from public sources (used in scene).
+- Summer MCP tools available.
+
+## Case 1: Happy Path — Steam (Windows + Mac + Linux)
+
+**Input:** "I'm ready to ship to Steam. Build me Windows, Mac, and Linux releases."
+
+**Expected MCP tool sequence (in order):**
+
+1. (Skill asks the destination question and waits — confirms Steam, Win/Mac/Linux.)
+2. Pre-flight:
+   - `summer_get_diagnostics` — clean
+   - `summer_get_console` — clean
+   - Read `project.godot` — main scene set, no version, no name
+   - Read `LICENSE` — does not exist
+   - Read `attribution.md` — does not exist
+   - Read `export_presets.cfg` — `debug = true` on all presets
+   - Grep for hardcoded paths
+3. (Skill lists the pre-flight failures: missing LICENSE, missing attribution.md, missing version, missing game name, debug=true on release presets, missing Steam-required assets like trailer + capsules.)
+4. Skill asks: "Pre-flight failed on N items: <list>. Want me to walk these one by one?"
+5. (Does NOT proceed to build.)
+
+**Assertions:**
+
+- [ ] Skill asks the destination question first.
+- [ ] Skill runs the FULL pre-flight checklist before any build.
+- [ ] Skill detects missing LICENSE and missing `attribution.md`.
+- [ ] Skill detects `debug = true` and flags it as a blocker for release.
+- [ ] Skill detects missing Steam-specific assets (capsules, trailer) and lists them.
+- [ ] Skill does NOT produce a build until the user fixes the blockers OR explicitly waives them.
+- [ ] Skill never auto-uploads to Steam Pipe — only points at the upload command.
+
+## Case 2: Failure Path — pre-flight passes, but iOS targeted without Apple Developer setup
+
+**Fixture:** Project is clean (LICENSE present, no script errors, version + name set).
+
+**Input:** "Ship to iOS App Store."
+
+**Expected behavior:**
+
+- Skill runs pre-flight — clean.
+- Skill walks iOS-specific requirements: 1024×1024 icon, screenshots at 6.5" iPhone resolution, App Store description, privacy policy URL, support URL, bundle ID, Apple Developer cert + provisioning profile.
+- Skill asks: "iOS submission requires (a) Apple Developer account ($99/yr), (b) Bundle ID configured in Apple Developer portal, (c) distribution certificate + provisioning profile, (d) macOS machine with Xcode for the final archive step. Do you have these set up? If not, those are the prerequisites — I can help with the build config but not the Apple Developer side."
+- Does NOT silently produce an unsigned `.ipa` that can't be submitted.
+
+**Assertions:**
+
+- [ ] Skill names the iOS prerequisites that aren't satisfiable from inside Godot.
+- [ ] Skill names the bundle-ID convention (`com.<org>.<game>`).
+- [ ] Skill mentions TestFlight before App Store review.
+- [ ] Skill does NOT pretend to do code signing it can't actually do.
+- [ ] Skill names AAB-vs-APK if the user mistakenly says "Android APK" (different ticket but related anti-pattern).
+
+## Case 3: Edge Case — multi-platform, web HTML5 included
+
+**Fixture:** Same as Case 1 but post-fix (LICENSE added, attribution.md added, presets `debug = false`, version = "1.0.0", screenshots ready, trailer recorded).
+
+**Input:** "Ship to Steam + itch + web."
+
+**Expected behavior:**
+
+- Pre-flight clean.
+- Skill walks each platform's requirements separately.
+- For web: explicitly flags the multiplayer transport (ENet doesn't work in browser), the audio autoplay block (Chrome blocks until first user click), and the file-size matters trap.
+- Web export preset configured: encryption disabled, no JS eval, GLES3 fallback to GLES2 on if old browsers targeted.
+- Skill asks: "May I produce 5 builds (Win + Mac + Linux + itch packages + web)?"
+- Produces builds via `godot --headless --export-release` invocations after user OK.
+- Verifies each build size and lists post-build warnings (e.g. "Web build is 180 MB — consider stripping unused textures").
+- Points at upload commands for each: `steamcmd`, `butler push`, manual itch web upload.
+
+**Assertions:**
+
+- [ ] Skill walks per-platform requirements separately, NOT a generic checklist.
+- [ ] For web: skill flags the autoplay + multiplayer + file-size traps explicitly.
+- [ ] Skill produces builds in correct order (build, then verify, then point at upload — never auto-upload).
+- [ ] Skill provides per-platform upload commands (steamcmd / butler / etc).
+- [ ] Skill does NOT execute uploads itself.
+
+## Case 4: No Summer MCP — fallback path
+
+**Fixture:** Same as Case 1, MCP unavailable.
+
+**Input:** "I want to ship to Steam."
+
+**Expected behavior:**
+
+- Skill detects MCP unavailable.
+- Asks user to confirm via the editor: main scene set, no errors in Output panel, no errors in Debugger panel.
+- Asks user to paste contents of `project.godot` and `export_presets.cfg`.
+- Walks the pre-flight checklist by reasoning over the pasted text.
+- Provides per-platform asset list and config recommendations.
+- Provides build commands the user can run manually (`godot --headless --export-release ...`).
+- Provides upload commands the user can run manually (`steamcmd ...`).
+- Still applies "May I write" before any file edit (e.g. `LICENSE` creation).
+
+**Assertions:**
+
+- [ ] Skill does not blindly call `summer_*` tools and fail.
+- [ ] Skill asks for the specific files it needs (project.godot, export_presets.cfg).
+- [ ] Skill still runs the full pre-flight check via reading.
+- [ ] Skill names the same blockers (LICENSE, debug=true, missing trailer).
+- [ ] Skill asks "May I write" before creating LICENSE / attribution.md / etc.
+
+---
+
+This spec runs via `/skill-test export-and-ship spec` (see `_meta/skill-test/SKILL.md`).

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

@@ -20,11 +20,11 @@
 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")`
+8. `summer_input_map_bind(name="move_forward", events=[{type:"key", key:"W"}])`
+9. `summer_input_map_bind(name="move_back", events=[{type:"key", key:"S"}])`
+10. `summer_input_map_bind(name="move_left", events=[{type:"key", key:"A"}])`
+11. `summer_input_map_bind(name="move_right", events=[{type:"key", key:"D"}])`
+12. `summer_input_map_bind(name="jump", events=[{type:"key", 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`

package/skills/_tests/specs/setup-multiplayer.md

@@ -0,0 +1,106 @@
+# Skill Spec: /setup-multiplayer
+
+## Fixture
+
+- Godot 4.5 / Summer Engine project, single-player game with `World/Player` (CharacterBody3D) and a working camera + movement script.
+- Summer MCP tools available.
+- Host file tools available (Read, Edit, Write).
+- No multiplayer setup yet (no autoloads, no MultiplayerSpawner, no Synchronizer).
+
+## Case 1: Happy Path — co-op LAN (2–4 players)
+
+**Input:** "Add multiplayer to my game. Co-op for me and three friends."
+
+**Expected MCP tool sequence (in order):**
+
+1. (Skill asks the four blocking questions — type / count / authority / network — and waits.)
+2. User confirms: co-op online, 4 players, host one of the players, public internet.
+3. (Skill explicitly states the locked decision: "Going with **host authority**, ENet transport, 30 Hz input / 20 Hz position. Refactoring authority later is brutal — confirm.")
+4. After user OK:
+   - `summer_get_scene_tree`
+   - `summer_inspect_node "./World/Player"`
+   - `Write scripts/network.gd` (autoload)
+   - `summer_project_setting(name="autoload/Network", value="*res://scripts/network.gd")`
+   - `summer_add_node(parent="./World/Players/Player", type="MultiplayerSynchronizer", name="Sync")` (or the equivalent on the player scene)
+   - SceneReplicationConfig saved as standalone `.tres` (NOT inline)
+   - `Write scripts/player_net.gd`
+   - `summer_save_scene`
+   - `summer_get_script_errors`
+
+**Assertions:**
+
+- [ ] Skill asks all four blocking questions BEFORE any tool call.
+- [ ] Skill explicitly names the authority model (host) and gets a confirmation before mutating.
+- [ ] Skill picks ENet (NOT custom transport, NOT WebRTC).
+- [ ] Generated script uses `MultiplayerSpawner` pattern (host spawns, clients receive).
+- [ ] Player script disables `_physics_process` for non-local peers.
+- [ ] Camera is local-only (`camera.current = is_local`).
+- [ ] Damage RPC checks `multiplayer.is_server()` before applying.
+- [ ] At least one `any_peer` RPC validates `get_remote_sender_id()`.
+- [ ] SceneReplicationConfig is a standalone `.tres`, NOT inline sub_resource.
+- [ ] Skill does NOT replicate cosmetic VFX or local UI.
+- [ ] Final step is `summer_save_scene` then `summer_get_script_errors`.
+
+## Case 2: Failure Path — user wants competitive PvP without dedicated server
+
+**Input:** "Add competitive PvP for 8 players, hosted by one of them, with anti-cheat."
+
+**Expected behavior:**
+
+- Skill names the conflict: "Anti-cheat with host-authority is fundamentally broken — the host can always cheat. For competitive PvP at this scale, you need a dedicated server. Want me to scaffold that path (different code, different deploy story), or are we doing trusted-host co-op-style PvP?"
+- Does NOT silently scaffold host-authority code that the user thinks has anti-cheat.
+- Does NOT scaffold dedicated-server code without explicit confirmation (different complexity).
+
+**Assertions:**
+
+- [ ] Skill flags the architectural impossibility, not just "this is hard".
+- [ ] Skill names the trade-off explicitly (host = host can cheat; dedicated = ops cost).
+- [ ] Skill stops to ask before generating any code.
+- [ ] Skill does NOT just pick host-authority because it's the default.
+
+## Case 3: Edge Case — user says "let's also do rollback netcode for our co-op"
+
+**Fixture:** Same as Case 1.
+
+**Input:** "Add multiplayer with rollback netcode so we don't see lag."
+
+**Expected behavior:**
+
+- Skill calls out: "Rollback netcode is a 6-month project on its own and is the right answer for fighting games / lock-step RTS, not co-op. For co-op, host authority + smooth interpolation gives you 95% of the perceived smoothness for 5% of the work. Want me to scaffold the standard host model?"
+- Does NOT start scaffolding rollback.
+- Does NOT silently downgrade to host-authority — names the choice and the trade-off.
+
+**Assertions:**
+
+- [ ] Skill names rollback as wrong-tool-for-job for co-op.
+- [ ] Skill names the standard alternative (host authority + interpolation).
+- [ ] Skill stops to confirm before scaffolding.
+- [ ] Skill points to specialist skill for lag compensation if user insists on competitive shooter.
+
+## Case 4: No Summer MCP — fallback path
+
+**Fixture:** Same as Case 1, but Summer MCP unavailable.
+
+**Input:** "Add co-op multiplayer for 4 players."
+
+**Expected behavior:**
+
+- Skill detects MCP unavailable.
+- Asks the user to paste their existing main scene `.tscn` so the autoload + spawn paths reference real nodes.
+- Asks the user to paste `project.godot` so the autoload entry can be added by hand.
+- Writes `scripts/network.gd` + `scripts/player_net.gd` directly via host file tools.
+- Provides a manual `project.godot` patch (autoload entry + replication config path) as text the user can paste.
+- Provides scene-editor instructions for adding the MultiplayerSynchronizer + setting up replication properties.
+- Still asks "May I write …" before each file write.
+
+**Assertions:**
+
+- [ ] Skill does not blindly call `summer_*` tools and fail.
+- [ ] Generated scripts compile in Godot 4.5 / Summer Engine.
+- [ ] Skill provides a `project.godot` patch in valid Godot project format.
+- [ ] Skill still asks for confirmation on each write.
+- [ ] Same opinionated decisions hold (host authority, ENet, no replication of cosmetic VFX).
+
+---
+
+This spec runs via `/skill-test setup-multiplayer spec` (see `_meta/skill-test/SKILL.md`).

package/skills/_tests/specs/tune-performance.md

@@ -0,0 +1,104 @@
+# Skill Spec: /tune-performance
+
+## Fixture
+
+- Godot 4.5 / Summer Engine project with a 3D scene.
+- Summer MCP tools available (engine running on localhost:6550).
+- Host file tools available (Read, Edit, Write).
+
+## Case 1: Happy Path — rendering hotspot (foliage)
+
+**Fixture:** `World/Foliage` contains 240 individual MeshInstance3D children, all using the same tree mesh. Game runs at ~22 fps, render time ~14 ms / frame.
+
+**Input:** "My game is slow when I look at the forest."
+
+**Expected MCP tool sequence (in order):**
+
+1. (Skill asks one focused question and waits — confirms it's framerate-drops-when-looking-at-X.)
+2. `summer_clear_console`
+3. `summer_play`
+4. (Skill asks user to look at the forest for 5–10 seconds.)
+5. `summer_get_diagnostics` — baseline numbers
+6. `summer_stop`
+7. (Skill identifies render time > 50% frame budget, dominant cost = rendering.)
+8. `summer_get_scene_tree` + `summer_inspect_node "./World/Foliage"` — confirms 240 MeshInstance3D children.
+9. (Skill states hypothesis: "240 MeshInstance3D = 240 draw calls. MultiMeshInstance3D will drop this to ~1.")
+10. (Skill asks: "May I refactor `./World/Foliage` to use a MultiMeshInstance3D? Expected render time: 14 ms → 3–5 ms.")
+11. After OK: applies fix, `summer_save_scene`, `summer_clear_console`, `summer_play`, `summer_get_diagnostics`, `summer_stop`.
+12. Reports before/after.
+
+**Assertions:**
+
+- [ ] Skill takes a baseline measurement BEFORE proposing a fix.
+- [ ] Skill identifies the dominant cost using actual numbers, not a guess.
+- [ ] Skill proposes ONE fix, not a bundle of three.
+- [ ] Proposal includes an expected metric movement (e.g. "14 ms → 3–5 ms").
+- [ ] Skill asks "May I" before mutating.
+- [ ] Skill re-measures after applying the fix and reports before/after.
+- [ ] Skill never optimizes physics or scripting in this scenario (since rendering was dominant).
+
+## Case 2: Failure Path — wrong subsystem hypothesis
+
+**Fixture:** Game stutters every ~3 seconds. User suspects "lag spikes from too many enemies".
+
+**Input:** "Game stutters every few seconds. I think it's the enemy AI."
+
+**Expected behavior:**
+
+- Skill resists the user's guess and takes a baseline.
+- `summer_get_diagnostics` shows: avg frame time fine, but periodic 80 ms spikes.
+- `summer_get_console` shows shader-compilation warnings: "Compiling SpatialMaterial #1234".
+- Skill identifies: this is shader compile jitter, not AI.
+- Skill says: "The spikes correlate with shader compilation, not the AI loop. Fix is a warmup pass on scene load (force-render off-screen to compile materials). Should I add the warmup pass?"
+
+**Assertions:**
+
+- [ ] Skill verifies via diagnostics + console BEFORE accepting the user's hypothesis.
+- [ ] Skill names the actual cause (shader compile) explicitly.
+- [ ] Skill does NOT optimize AI code that wasn't the cause.
+- [ ] Skill proposes a targeted fix (warmup) rather than a generic one.
+
+## Case 3: Edge Case — Summer MCP available but engine not currently running
+
+**Fixture:** Same as Case 1 but the engine is open and idle, not playing.
+
+**Input:** "Why is my game slow?"
+
+**Expected behavior:**
+
+- Skill calls `summer_is_running` → false.
+- Skill explains: "I need to play the game and reproduce the slowdown to get real numbers."
+- Asks user permission: "May I `summer_play` and ask you to reproduce the slow scenario?"
+- After OK: runs the play → reproduce → diagnostics → stop loop.
+- Does NOT skip baseline measurement and just guess from reading code.
+
+**Assertions:**
+
+- [ ] Skill checks `summer_is_running` first.
+- [ ] Skill asks before invoking `summer_play`.
+- [ ] Skill insists on baseline numbers before fixing anything.
+- [ ] Skill does NOT skip straight to "let me read your scripts and guess".
+
+## Case 4: No Summer MCP — fallback path
+
+**Fixture:** Same as Case 1, but Summer MCP unavailable.
+
+**Input:** "My forest scene is slow."
+
+**Expected behavior:**
+
+- Skill detects MCP unavailable.
+- Asks the user to enable Godot's Monitor panel (`Debug → Monitors`) and paste at minimum: FPS, frame time (ms), draw calls, video/video memory used, physics active objects.
+- Reasons over the pasted numbers the same way it would over diagnostics.
+- Continues with hypothesis → proposal → "May I edit?" → manual verification (asks the user to re-run and paste new numbers).
+
+**Assertions:**
+
+- [ ] Skill does not blindly call `summer_*` tools and fail.
+- [ ] Skill asks for the specific numbers it needs (not a vague "tell me more").
+- [ ] Skill still anchors on baseline-first, ONE-fix-at-a-time loop.
+- [ ] Skill names the dominant cost from the user-pasted numbers.
+
+---
+
+This spec runs via `/skill-test tune-performance spec` (see `_meta/skill-test/SKILL.md`).

package/skills/_tests/specs/vfx.md

@@ -0,0 +1,98 @@
+# Skill Spec: /vfx
+
+## Fixture
+
+- Godot 4.5 / Summer Engine project, main scene with `World/Player` (CharacterBody3D + Camera3D) and `World/Enemy` (CharacterBody3D + MeshInstance3D + a `damaged` signal on a script).
+- Summer MCP tools available (engine running on localhost:6550).
+- Host file tools available (Read, Edit, Write).
+
+## Case 1: Happy Path — combat hits feel flat
+
+**Input:** "My combat feels flat. Add some juice."
+
+**Expected behavior:**
+
+1. Skill asks one focused question: "What feels flat? combat hits / movement / pickups / damage / explosions / spell casts."
+2. User says "combat hits".
+3. Skill calls `summer_get_scene_tree`, then `summer_inspect_node "./World/Enemy"` to confirm a MeshInstance3D and a `damaged` signal exist.
+4. Skill proposes hit flash + camera shake bundle: "I'm about to add HitFlash on `./World/Enemy`, attach `scripts/hit_flash.gd`, attach `scripts/camera_shake.gd` to `./World/Player/Camera3D`, and connect the `damaged` signal. OK?"
+5. After user OK:
+   - `summer_add_node(parent="./World/Enemy", type="Node", name="HitFlash")`
+   - `Write scripts/hit_flash.gd`
+   - `Write scripts/camera_shake.gd`
+   - `summer_connect_signal(from="./World/Enemy", signal="damaged", to="./World/Enemy/HitFlash", method="flash")`
+   - `summer_save_scene`
+   - `summer_get_script_errors`
+
+**Assertions:**
+
+- [ ] Skill asks the "what feels flat?" question before any tool call.
+- [ ] Skill reads the scene tree and inspects the relevant node before adding nodes.
+- [ ] Skill explicitly states the bundle of changes and asks "May I" / "OK?" before mutation.
+- [ ] HitFlash script uses Tween + `set_surface_override_material`, NOT a polled timer in `_process`.
+- [ ] CameraShake uses quadratic falloff (`_trauma * _trauma`), NOT linear.
+- [ ] Skill never calls `summer_set_resource_property` on an inline sub_resource (e.g. ParticleProcessMaterial).
+- [ ] Skill ends with `summer_save_scene` then `summer_get_script_errors`.
+- [ ] Final hit flash duration is 0.06–0.12 sec (NOT 0.3 sec).
+
+## Case 2: Failure Path — no Camera3D in scene
+
+**Fixture:** `World/Player` exists but has no Camera3D child. User asks for screen shake.
+
+**Input:** "Add screen shake when I take damage."
+
+**Expected behavior:**
+
+- Skill calls `summer_get_scene_tree` and `summer_inspect_node "./World/Player"`, sees no Camera3D.
+- Skill does NOT silently spawn a Camera3D — it asks: "I don't see a Camera3D under `./World/Player`. Should I add one (and risk conflicting with an existing camera elsewhere), or do you have a camera node I should target?"
+- Waits for the answer.
+
+**Assertions:**
+
+- [ ] Skill detects the missing Camera3D and stops to ask.
+- [ ] Skill does NOT add a Camera3D unilaterally.
+- [ ] Skill names a concrete next-step path (point to existing camera OR add new one explicitly).
+
+## Case 3: Edge Case — user wants "all the juice"
+
+**Fixture:** Same as Case 1.
+
+**Input:** "Add all the VFX. Make it feel like Hades."
+
+**Expected behavior:**
+
+- Skill resists the temptation to stack 5 recipes at once.
+- Anchors on combat hits first (per skill's own guidance: "loudest perceived improvement per minute spent").
+- Says: "I'd rather land hit-flash + screen-shake first so we can see them work, then stack pickups/explosions next. Sound good?"
+- Does NOT propose a single bundle of 5 recipes.
+
+**Assertions:**
+
+- [ ] Skill explicitly chooses ONE recipe to start with, not all.
+- [ ] Skill names "combat hits" as the anchor.
+- [ ] Skill defers other recipes to a follow-up pass.
+
+## Case 4: No Summer MCP — file-edit fallback
+
+**Fixture:** Same as Case 1, but Summer MCP is unavailable (Cursor in a project where the engine is not connected).
+
+**Input:** "Add a hit flash to my enemy."
+
+**Expected behavior:**
+
+- Skill detects MCP unavailable.
+- Asks the user to paste the relevant `.tscn` snippet (the Enemy node + its children) so the skill can write the right node-path references.
+- Writes `scripts/hit_flash.gd` directly via host file tools.
+- Provides a `.tscn` patch (or step-by-step manual editor instructions) for adding the HitFlash node and connecting the signal — does NOT blindly call `summer_*` tools.
+- Still asks "May I write `scripts/hit_flash.gd`?" before each file write.
+
+**Assertions:**
+
+- [ ] Skill identifies MCP is unavailable and adapts.
+- [ ] Generated GDScript is syntactically valid Godot 4 GDScript with type hints.
+- [ ] Skill asks the user to paste the `.tscn` snippet for accurate node paths.
+- [ ] Skill still applies the "May I write …" protocol on file writes.
+
+---
+
+This spec runs via `/skill-test vfx spec` (see `_meta/skill-test/SKILL.md`).