summer-engine 2.2.0 → 2.5.0

package/skills/_tests/specs/audio-direction.md

@@ -1,123 +0,0 @@
-# Skill Spec: /audio-direction
-
-## Fixture
-
-- Godot 4.5 / Summer Engine project, default audio bus layout (Master only).
-- `.summer/GameSoul.md` exists; brief: "Cozy farming sim, vertical slice scope."
-- `.summer/art-bible.md` exists; mood: "soft, hand-warmed, golden-hour, painterly".
-- No `.summer/audio-bible.md` yet.
-- No `audio/` folder yet.
-- Summer MCP available.
-
-## Case 1: Happy Path — define audio direction for cozy farming sim
-
-**Input:** "Define the audio direction. References: Stardew Valley OST, Studio Ghibli scores, and Outer Wilds. Acoustic, organic SFX."
-
-**Expected MCP tool sequence (in order):**
-
-1. `Read .summer/GameSoul.md` — anchor to brief
-2. `Read .summer/art-bible.md` — anchor to visual mood
-3. (Skill notes the rhyme: "soft, hand-warmed, golden-hour" + acoustic references = acoustic / folk style as primary)
-4. (Skill walks: music style → tempo + key → SFX vocabulary (8 classes) → dynamic music plan with state machine → spatial + mix rules)
-5. (Skill shows the bible inline)
-6. (Skill asks: "May I create `audio/default_bus_layout.tres` with these buses: Master / Music / SFX / UI / Voice / Ambient / Reverb_Small / Reverb_Large / Reverb_Outdoor?")
-7. `Write audio/default_bus_layout.tres`
-8. `summer_project_setting(key="audio/buses/default_bus_layout", value="res://audio/default_bus_layout.tres")`
-9. (Skill asks: "May I create `.summer/audio-bible.md` with this bible?")
-10. `Write .summer/audio-bible.md`
-11. (Skill optionally asks: "May I generate first-pass SFX seeds for UI, pickup, damage?")
-12. (On yes) `summer_generate_audio(prompt="soft woody UI click, 80ms, no reverb", duration=0.1)` etc.
-
-**Assertions:**
-
-- [ ] Skill reads BOTH `.summer/GameSoul.md` AND `.summer/art-bible.md` to anchor.
-- [ ] Skill enforces 3+ references — does not proceed with one or two.
-- [ ] Skill picks ONE primary music style; if user pitches multiple, names the conflict.
-- [ ] Music section has explicit tempo range (BPM), key center, time signature — not "varies".
-- [ ] SFX vocabulary has 8 classes, each with character + examples + a DON'T rule.
-- [ ] DON'T rules include things like "no pure sine ding for pickup" and "no same footstep for all surfaces".
-- [ ] Dynamic music plan picks ONE model (layered / vertical / horizontal / procedural) — not a list.
-- [ ] Dynamic music plan defines a state machine with named states + transitions + crossfade times.
-- [ ] Spatial + mix section has concrete dB values, attenuation curve, max distance, master ceiling -1 dBTP.
-- [ ] Mix defaults to SFX 0 dB / Music -8 dB / UI -3 dB (SFX loudest).
-- [ ] Bus layout has at least Music, SFX, UI, Voice, Ambient + 1+ Reverb send buses.
-- [ ] Skill asks "May I ..." before any `Write`, `summer_project_setting`, or `summer_generate_audio` call.
-- [ ] Skill writes `.summer/audio-bible.md` only after asking.
-- [ ] Skill never calls `summer_set_resource_property` on an inline sub_resource (silent-fail trap).
-- [ ] Skill ends with routing to `/summer:design-mechanic` or implementation skill.
-
-## Case 2: Failure Path — references contradict the brief
-
-**Fixture:** Same as Case 1, but brief says "horror walking sim".
-
-**Input:** "References: Mario 64 OST, A Hat in Time, Banjo-Kazooie. Bouncy chiptune."
-
-**Expected behavior:**
-
-- Skill identifies the conflict: "Brief says horror; references are bright N64 platformer scores. Those want opposite shapes — horror wants ambient drone or industrial; bouncy chiptune undercuts dread."
-- Skill asks the user to resolve: "(a) keep horror brief, change references to ambient/industrial, (b) keep bouncy references, change brief away from horror, or (c) intentional juxtaposition (rare; works in 1 in 50 games — Undertale, Buckshot Roulette)."
-- Skill does NOT silently pick or design a "horror chiptune" hybrid without flagging the friction.
-
-**Assertions:**
-
-- [ ] Skill names the brief vs. references conflict explicitly.
-- [ ] Skill explains *why* the shapes oppose.
-- [ ] Skill offers (c) intentional juxtaposition as a valid but rare path.
-- [ ] No bible written until the user resolves.
-
-## Case 3: Edge Case — user wants no music
-
-**Fixture:** Same as Case 1.
-
-**Input:** "Reference: Inside, Limbo. No music — just diegetic sound and ambience."
-
-**Expected behavior:**
-
-- Skill accepts "no music" as a valid direction (those references genuinely use it).
-- Skill replaces the dynamic music plan section with a "Diegetic-only ambience plan":
-  - Named ambience layers (room tone / wind / distant water / heart-rate-tied sub-bass when tense)
-  - Rules for when sub-bass enters (proximity to threat) and exits
-  - SFX still gets all 8 vocabulary classes (with extra weight on the "Ambient layer" class)
-- Skill keeps the bus layout but removes the Music bus or marks it "reserved (unused in v1)".
-- Skill notes the trade-off: "Diegetic-only is harder to make feel paced — every level needs an ambient arc that does what music would normally do."
-
-**Assertions:**
-
-- [ ] Skill does NOT force a music style on a no-music game.
-- [ ] Bible has a Diegetic / ambience plan section instead of (or supplementing) Dynamic music plan.
-- [ ] Bus layout reflects the choice (no Music bus or marked reserved).
-- [ ] Skill flags the trade-off: pacing is now ambience's job.
-
-## Case 4: No Summer MCP — file-edit fallback
-
-**Fixture:** Same as Case 1, but Summer MCP is unavailable.
-
-**Input:** "Define the audio direction for my cozy farming sim."
-
-**Expected behavior:**
-
-- Skill detects no MCP.
-- Walks the design beats normally.
-- Instead of `summer_project_setting`, prints the `project.godot` snippet for the user to paste:
-
-  ```
-  [audio]
-  buses/default_bus_layout="res://audio/default_bus_layout.tres"
-  ```
-
-- Generates `audio/default_bus_layout.tres` content as plain text for the user to save (Godot's `.tres` resource format with bus entries).
-- Writes `.summer/audio-bible.md` via host `Write`.
-- Does NOT call `summer_generate_audio` — instead suggests external SFX library searches or asks the user to handle generation later.
-- Asks "May I write ..." before each file write.
-
-**Assertions:**
-
-- [ ] Skill identifies that MCP is unavailable; does not blindly call `summer_*`.
-- [ ] Generated `project.godot` snippet uses correct INI section format.
-- [ ] Generated `default_bus_layout.tres` is valid Godot 4 resource format.
-- [ ] Skill still writes `.summer/audio-bible.md`.
-- [ ] Skill does not attempt audio generation when generation tools are unavailable.
-
----
-
-This spec runs via `/skill-test audio-direction spec` (see `_meta/skill-test/SKILL.md`).

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

@@ -1,99 +0,0 @@
-# Skill Spec: /brainstorm-game
-
-## Fixture
-
-- Empty Godot 4.5 / Summer Engine project, `project.godot` exists, no `.summer/` folder yet.
-- Summer MCP available.
-- Host file tools available (Read, Write, Edit).
-
-## Case 1: Happy Path — fresh idea, full brainstorm
-
-**Input:** "I want to make a game but I don't know what."
-
-**Expected behavior:**
-
-1. Skill asks the one opening question: "One sentence — what kind of game do you want to make?"
-2. (Simulated user reply: "Something like Hades, but cozy.")
-3. Skill recognizes Action-Combat anchor + cozy modifier, picks Action-Combat branch, but flags the tension: "Hades is tense, cozy is calm — let's pin which side wins."
-4. Skill walks: core loop candidate → user refinement → three mechanics (push back if user lists more) → one-phrase art direction → scope (recommend vertical slice).
-5. Skill drafts the 1-page brief inline, shows it to the user.
-6. Skill asks: "May I create `.summer/GameSoul.md` with this brief?"
-7. On yes, calls `Write .summer/GameSoul.md`.
-8. Skill ends with the routing question pointing to `/summer:design-mechanic` or similar.
-
-**Assertions:**
-
-- [ ] Skill asks ONLY the opening question first, no menu of options.
-- [ ] Skill picks ONE branch, not multiple; doesn't ask 6 questions in parallel.
-- [ ] Skill enforces the three-mechanic limit (pushes back if user lists more).
-- [ ] Brief includes all 8 fields: Pitch, Core loop, Three mechanics, Art direction, Scope, Win condition, "One thing this is NOT", Inspirations, Parked for later.
-- [ ] Skill asks "May I create `.summer/GameSoul.md`?" before writing.
-- [ ] Brief is shown inline before being written so the user can react.
-- [ ] Skill ends with a routing question to a next `/summer:` step.
-- [ ] Skill defaults to "vertical slice" scope when the user is unsure.
-
-## Case 2: Failure Path — `.summer/GameSoul.md` already exists
-
-**Fixture:** Same as Case 1, except `.summer/GameSoul.md` already exists with a previous game's brief.
-
-**Input:** "I want to brainstorm a new game."
-
-**Expected behavior:**
-
-- Skill reads the existing `.summer/GameSoul.md` first via `Read`.
-- Skill walks the brainstorm normally.
-- Before writing, skill detects the file exists and asks: "`.summer/GameSoul.md` already exists. May I overwrite it, or merge into a 'Revision 2' section below the existing brief?"
-- Does NOT silently overwrite.
-
-**Assertions:**
-
-- [ ] Skill reads existing `.summer/GameSoul.md` before drafting the new brief.
-- [ ] Skill shows the user what would change before writing.
-- [ ] Skill explicitly offers overwrite vs. merge — does not default-pick.
-- [ ] No `Write` call happens until the user answers.
-
-## Case 3: Edge Case — user pitches a multiplayer 4-player co-op horror RPG with crafting
-
-**Fixture:** Same as Case 1.
-
-**Input:** "I want a 4-player online co-op horror RPG with crafting, base-building, dialogue trees, and procedural worlds, kind of like Valheim meets Phasmophobia meets Disco Elysium."
-
-**Expected behavior:**
-
-- Skill catches the multiplayer flag (4-player co-op = scope explosion) and surfaces it explicitly: "Multiplayer is its own scope category — it roughly 3x's everything. Confirm: is multiplayer non-negotiable, or could a great single-player version land first and multiplayer come later?"
-- Skill enforces the three-mechanic constraint hard. Names which mechanics from the user's pitch are content vs. mechanics, e.g.: "crafting + base-building are systems, not mechanics; dialogue is a mechanic if choices change outcomes."
-- Skill states a sanity-check concern: "Procedural worlds + horror + RPG depth + multiplayer at vertical-slice scope is unrealistic. Suggest scoping to one of those four pillars."
-- Skill does NOT just write the brief with all five things in it.
-- Skill asks the user to pick the cut.
-
-**Assertions:**
-
-- [ ] Skill flags multiplayer explicitly and asks about negotiability before continuing.
-- [ ] Skill distinguishes "system/feature" from "mechanic" out loud.
-- [ ] Skill names a scope concern instead of writing the brief verbatim from the pitch.
-- [ ] Skill never writes a brief with more than three mechanics.
-- [ ] Skill offers a clear cut, not a vague "scope down" platitude.
-
-## Case 4: No Summer MCP / no host file write — fallback path
-
-**Fixture:** Same as Case 1, except the host has no file-write tool (read-only agent in a constrained environment).
-
-**Input:** "Help me brainstorm a game."
-
-**Expected behavior:**
-
-- Skill detects no write tool is available.
-- Walks the brainstorm normally.
-- Instead of asking "May I create `.summer/GameSoul.md`?", prints the full brief to the user with explicit save instruction: "Save this as `.summer/GameSoul.md` in your project root. Every Summer skill reads it."
-- Still ends with the routing question.
-
-**Assertions:**
-
-- [ ] Skill does NOT call a file-write tool that doesn't exist.
-- [ ] Skill prints the brief inline as a self-contained block.
-- [ ] Skill includes the explicit save instruction with the canonical path.
-- [ ] Skill still asks the user the brainstorm questions and the routing question.
-
----
-
-This spec runs via `/skill-test brainstorm-game spec` (see `_meta/skill-test/SKILL.md`).

package/skills/_tests/specs/debug.md

@@ -1,94 +0,0 @@
-# Skill Spec: /debug
-
-## Fixture
-
-- A Godot/Summer project with one or more reproducible bugs.
-- Summer Engine running, MCP available.
-- Host file tools available (Read, Edit, Write).
-
-## Case 1: Happy Path — runtime error with clear stack trace
-
-**Fixture:** `scripts/player.gd` has `velocity.y -= GRAVTY * delta` (typo: GRAVTY instead of GRAVITY). Player crashes on `_physics_process` first frame.
-
-**Input:** "Debug my game. The player crashes the moment I press play."
-
-**Expected MCP tool sequence (in order):**
-
-1. (Skill asks the user one clarifying question and waits.)
-2. `summer_get_script_errors` — finds `Identifier "GRAVTY" not declared` at scripts/player.gd:14
-3. (Optional: `summer_get_console` to confirm no other errors hiding)
-4. `Read scripts/player.gd` — read 20–40 lines around line 14
-5. (Skill states hypothesis: typo, GRAVTY → GRAVITY)
-6. (Skill asks: "May I edit `scripts/player.gd` to rename GRAVTY → GRAVITY?")
-7. `Edit scripts/player.gd` — apply fix on user OK
-8. `summer_get_script_errors` — verify clean
-
-**Assertions:**
-
-- [ ] Skill asks for the user's description before any tool call.
-- [ ] First diagnostic tool called is `summer_get_script_errors` (cheapest).
-- [ ] Skill does NOT grep the whole codebase before reading the error.
-- [ ] Skill reads only the file + lines indicated by the error, not the whole file.
-- [ ] Skill states a single specific hypothesis before proposing a fix.
-- [ ] Skill asks "May I edit …" before writing.
-- [ ] After the fix, skill re-runs `summer_get_script_errors` to verify.
-- [ ] Skill never calls `summer_set_resource_property` on an inline sub-resource (silent-fail trap).
-
-## Case 2: Failure Path — bug only reproduces at runtime
-
-**Fixture:** Game compiles fine but crashes when player picks up a coin: `Invalid call. Nonexistent function 'play' in base 'Nil'.` AudioStreamPlayer node was deleted in editor but pickup script still references it.
-
-**Input:** "When I pick up a coin, the game crashes."
-
-**Expected behavior:**
-
-- Skill calls `summer_get_script_errors` first → clean.
-- Skill realizes it's runtime: `summer_clear_console`, `summer_play`.
-- Skill asks user: "Reproduce the bug now — pick up a coin."
-- After confirmation, calls `summer_get_debugger_errors`.
-- Stack trace points to `coin.gd:32`, function `_on_body_entered`, calling `audio.play()` where `audio` is `null`.
-- Skill calls `summer_inspect_node "./Coin/AudioStreamPlayer"` to confirm the node is missing.
-- Skill proposes: re-add the AudioStreamPlayer (via `summer_add_node`) OR null-check in code.
-- Asks the user which.
-
-**Assertions:**
-
-- [ ] Skill recognizes that script-errors-clean + crash-on-runtime = runtime-only bug.
-- [ ] Skill explicitly invokes the play→reproduce→read-debugger loop, not just one shot.
-- [ ] Skill verifies the missing-node hypothesis with `summer_inspect_node` BEFORE editing code.
-- [ ] Skill offers BOTH options (fix scene OR fix code) instead of unilaterally picking.
-
-## Case 3: Edge Case — user gives a vague description
-
-**Fixture:** Same as Case 1.
-
-**Input:** "Something's broken."
-
-**Expected behavior:**
-
-- Skill asks one focused follow-up: "What's happening, and when?"
-- Does NOT start grepping code or running tools blindly.
-
-**Assertions:**
-
-- [ ] No tool calls happen until the user gives a concrete symptom.
-- [ ] Skill's follow-up is one short question, not a checklist.
-
-## Case 4: No Summer MCP — fallback path
-
-**Fixture:** Same as Case 1, but Summer MCP is unavailable (engine not connected).
-
-**Input:** "Debug my game."
-
-**Expected behavior:**
-
-- Skill detects MCP unavailable.
-- Asks the user to copy-paste from Godot's Output and Debugger panels.
-- Reasons over the pasted text the same way it would over MCP output.
-- Continues with the rest of the workflow (read code, hypothesize, propose fix).
-
-**Assertions:**
-
-- [ ] Skill does not blindly call `summer_*` tools and fail.
-- [ ] Skill explicitly asks for the panel output instead of guessing.
-- [ ] The rest of the loop (hypothesis → "May I edit?" → verify) still runs.

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

@@ -1,113 +0,0 @@
-# Skill Spec: /design-level
-
-## Fixture
-
-- Godot 4.5 / Summer Engine project, main scene already has a `World/Player` (CharacterBody3D) with FPS controller wired.
-- `.summer/GameSoul.md` exists; brief: "Action-combat game, three mechanics: dash, parry, double-jump. Vertical slice scope."
-- `.summer/mechanics/parry.md` exists.
-- No `levels/` folder yet.
-- Summer MCP available.
-
-## Case 1: Happy Path — design level 1, a combat encounter
-
-**Input:** "Design level 1, a 5-minute combat encounter that teaches parry."
-
-**Expected MCP tool sequence (in order):**
-
-1. `Read .summer/GameSoul.md` — anchor to the brief
-2. (Optional: `Read .summer/mechanics/parry.md` — anchor to the mechanic being taught)
-3. (Skill walks: type → teaching goal → pacing curve (5 beats with intensity numbers) → encounters list → secrets list → reward gating → spaces list)
-4. (Skill shows the node-tree skeleton inline)
-5. (Skill asks: "May I create `levels/level_01.tscn` with this skeleton?")
-6. `summer_create_scene(path="res://levels/level_01.tscn", root_type="Node3D", root_name="World")`
-7. `summer_add_node(parent="./World", type="Node3D", name="Geometry")` and children
-8. `summer_add_node(parent="./World", type="Node3D", name="Spawns")` and children
-9. `summer_add_node(parent="./World", type="Node3D", name="Triggers")` and Area3D children
-10. `summer_add_node(parent="./World", type="Node3D", name="Pickups")`
-11. `summer_add_node(parent="./World", type="Node3D", name="Secrets")`
-12. `summer_add_node(parent="./World", type="Node3D", name="Lighting")` with WorldEnvironment + DirectionalLight3D
-13. `summer_save_scene`
-14. (Skill asks: "May I create `.summer/levels/level_01.md` with the design doc?")
-15. `Write .summer/levels/level_01.md`
-16. `summer_get_script_errors`
-
-**Assertions:**
-
-- [ ] Skill reads `.summer/GameSoul.md` to anchor.
-- [ ] Skill reads the relevant `.summer/mechanics/<name>.md` if the level teaches an existing mechanic.
-- [ ] Skill states a concrete teaching goal — not a vague "fun encounter".
-- [ ] Skill draws a 5-beat pacing curve with intensity numbers (Intro / Build / Peak / Release / Hook).
-- [ ] Skill lists 4 encounters with timing + space mapping.
-- [ ] Skill lists 3 secrets with which beat each lives in.
-- [ ] Skill lists reward gating, gates rewards behind tests.
-- [ ] Skill enforces 4-6 distinct spaces (does not produce 12 micro-rooms).
-- [ ] Skill asks "May I create ..." before `summer_create_scene`.
-- [ ] Skeleton is markers + Area3Ds, NOT meshes / enemy scripts (those come later).
-- [ ] Skill writes the design doc to `.summer/levels/<name>.md`.
-- [ ] Skill never calls `summer_set_resource_property` on an inline sub_resource.
-- [ ] Final step is `summer_save_scene` then `summer_get_script_errors`.
-
-## Case 2: Failure Path — user blends three level types
-
-**Fixture:** Same as Case 1.
-
-**Input:** "Design a stealth level with a puzzle in the middle and a boss at the end."
-
-**Expected behavior:**
-
-- Skill recognizes blended types: stealth + puzzle + boss.
-- Skill pushes back: "That's three level types. Pick one as the primary; the other two become flavor or get split into sequential levels."
-- Skill names the trade-off: "Stealth + boss in the same level kills both — stealth wants tension that releases at the encounter, boss wants tension that builds *to* the encounter. They're opposite shapes."
-- Skill does NOT silently pick one or design all three at once.
-
-**Assertions:**
-
-- [ ] Skill identifies the blend explicitly.
-- [ ] Skill explains the design tension between the blended types.
-- [ ] Skill asks the user to pick one primary type before designing.
-- [ ] No `summer_create_scene` call until user picks.
-
-## Case 3: Edge Case — no `.summer/GameSoul.md` exists
-
-**Fixture:** Same as Case 1, but `.summer/GameSoul.md` does NOT exist.
-
-**Input:** "Design level 1 of my game."
-
-**Expected behavior:**
-
-- Skill detects no brief exists.
-- Skill suggests: "No `.summer/GameSoul.md` yet — without a brief, this level has no game to serve. Run `/summer:brainstorm-game` first, or give me the core loop + mechanics inline so I can anchor the design."
-- Skill does NOT design a generic level in a vacuum.
-
-**Assertions:**
-
-- [ ] Skill checks for `.summer/GameSoul.md` early (before designing).
-- [ ] Skill explicitly recommends `/summer:brainstorm-game` if absent.
-- [ ] Skill offers the inline-anchor alternative as a fallback.
-- [ ] No design happens without anchoring information.
-
-## Case 4: No Summer MCP — file-edit fallback
-
-**Fixture:** Same as Case 1, but Summer MCP is unavailable.
-
-**Input:** "Design level 1 — a 5-minute combat encounter."
-
-**Expected behavior:**
-
-- Skill detects no MCP.
-- Walks the design beats normally.
-- Instead of `summer_create_scene` + `summer_add_node`, prints the full `.tscn` file contents for the user to save manually at `levels/level_01.tscn`.
-- Generated `.tscn` is syntactically valid Godot 4 scene format with the marker/Area3D skeleton (no meshes).
-- Still writes the design doc to `.summer/levels/level_01.md` via host `Write`.
-- Asks "May I write ..." before each file write.
-
-**Assertions:**
-
-- [ ] Skill identifies that MCP is unavailable; does not blindly call `summer_*`.
-- [ ] Generated `.tscn` is parseable Godot 4 scene file.
-- [ ] Skeleton in the `.tscn` matches the spaces / spawns / triggers structure from the design doc.
-- [ ] Skill still writes `.summer/levels/<name>.md`.
-
----
-
-This spec runs via `/skill-test design-level spec` (see `_meta/skill-test/SKILL.md`).

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

@@ -1,112 +0,0 @@
-# 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`).