summer-engine 2.8.2 → 3.1.0

package/library/skills/agent-playtesting/resource.yaml

@@ -0,0 +1,52 @@
+id: skill/agent-playtesting
+kind: skill
+version: 1.0.0
+summary: Playtest by driving the LIVE game — deterministic launch, frame-stamped probes before/after each action, exact frame steps, scripted or recorded input.
+use_when:
+  - proving a gameplay feature works by driving the running game frame by frame with the runtime tools (summer_game_probe, summer_game_input, summer_game_control, summer_runtime_set/call/spawn/animate)
+  - a bug repro or an A/B needs a deterministic launch (seed, fixed frame rate, offscreen instance), a recorded input replay, or two instances side by side
+  - deciding what counts as evidence for "it moved / it fired / the node appeared" — the probe-before, probe-after, frame-stamped discipline
+  - asserting exact positions or timings by advancing the live game a physics frame at a time
+do_not_use_when:
+  - static or code-layer checks — verification-before-completion (compile, diagnostics) comes first
+  - a hidden disposable probe run is enough or the engine build lacks the runtime-control ops (Summer Engine 0.5.66 or newer) — playtesting-a-feature's RunVerification loop still applies there
+  - the feature works but feels wrong — debugging-game-feel
+facets:
+  lifecycle:
+    - build
+  domains:
+    - runtime
+    - playtest
+    - verification
+    - agent-workflow
+  modalities:
+    - project
+    - scenes
+compatibility:
+  engine: ">=4.6"
+related:
+  tools:
+    - tool/play
+    - tool/stop
+    - tool/is-running
+    - tool/game-probe
+    - tool/game-control
+    - tool/game-input
+    - tool/runtime-set
+    - tool/runtime-call
+    - tool/runtime-spawn
+    - tool/runtime-animate
+    - tool/get-runtime-tree
+    - tool/inspect-runtime-node
+    - tool/get-debugger-errors
+    - tool/screenshot
+  skills:
+    - skill/playtesting-a-feature
+    - skill/verifying-scenes
+    - skill/verification-before-completion
+    - skill/debugging-game-feel
+    - skill/investigating-bugs
+source: official
+license: MIT
+status: preview
+recommended: true

package/library/skills/ambient-bed/resource.yaml

@@ -0,0 +1,24 @@
+id: skill/ambient-bed
+kind: skill
+version: 1.0.2
+summary: Generate a long looping location ambience — forest, dungeon, city, spaceship, cave — a looping AudioStreamPlayer on the Ambient bus with a seamless loop.
+use_when:
+  - generating a long looping location ambience — forest at dawn, dungeon air, city street, spaceship hum, cave drip — non-melodic and low-energy
+  - a location feels silent and needs a continuous soundscape beneath the score and effects
+facets:
+  lifecycle:
+    - build
+  domains:
+    - audio
+    - assets
+  modalities:
+    - audio
+    - scenes
+compatibility:
+  engine: ">=4.6"
+source: official
+license: MIT
+status: stable
+recommended: false
+aliases:
+  - skills/audio/ambient-bed

package/{skills/video → library/skills}/animated-loop/SKILL.md

@@ -221,4 +221,4 @@ Once the loop is wired:
 - `audio/music-track` — score the menu.
 - `2d-assets/ui-graphics` — logo, menu buttons, HUD that sits over the loop.
 - `2d-assets/concept-art` — produce the reference still that anchors the loop.
-- `../../../references/mcp-tools-reference.md` — `summer_generate_video` parameter schema and error codes.
+- `../../references/mcp-tools-reference/mcp-tools-reference.md` — `summer_generate_video` parameter schema and error codes.

package/library/skills/animated-loop/resource.yaml

@@ -0,0 +1,27 @@
+id: skill/animated-loop
+kind: skill
+version: 1.0.4
+summary: Generate a short seamlessly-looping video clip — splash background, animated logo backdrop, idle title-screen footage — wired as a looping VideoStreamPlayer.
+use_when:
+  - generating a short looping video clip — splash screen background, animated logo backdrop, idle title-screen footage, looping environment ambience
+  - an idle backdrop behind the UI needs subtle motion without a real-time animated scene
+facets:
+  lifecycle:
+    - build
+  domains:
+    - video
+    - assets
+  modalities:
+    - video
+    - assets
+compatibility:
+  engine: ">=4.6"
+related:
+  skills:
+    - skill/asset-strategy
+source: official
+license: MIT
+status: stable
+recommended: false
+aliases:
+  - skills/video/animated-loop

package/{skills/animation → library/skills}/animation-tree/SKILL.md

@@ -5,7 +5,7 @@ license: MIT
 compatibility: [Cursor, Claude Code, Windsurf, Codex]
 category: animation
 user-invocable: false
-allowed-tools: Read Grep Edit Write summer_get_scene_tree summer_inspect_node summer_inspect_resource summer_add_node summer_set_prop summer_set_resource_property summer_save_scene summer_get_script_errors
+allowed-tools: Read Grep Edit Write summer_get_scene_tree summer_inspect_node summer_inspect_resource summer_run_script summer_add_node summer_set_prop summer_set_resource_property summer_connect_signal summer_save_scene summer_get_script_errors summer_play summer_stop
 paths: ["**/*.gd", "**/*.tscn", "**/*.tres"]
 ---
 
@@ -36,8 +36,8 @@ Before adding the tree, prove direct `AnimationPlayer.play()` visibly moves the
 
 - Single-clip looping background prop (banner waving, water surface). Just `AnimationPlayer.play("loop")` is fine.
 - Cinematic with hand-authored timing. Use `AnimationPlayer` directly with `play_with_capture`; AnimationTree is overkill.
-- Character has zero clips — generate first via `summer:animation/generate-motion`.
-- Procedural-only animation (no clips, all IK). That's `summer:animation/procedural-animation`.
+- Character has zero clips — generate first via `generate-motion`.
+- Procedural-only animation (no clips, all IK). That's `procedural-animation`.
 
 ## Canonical state machine
 
@@ -65,6 +65,15 @@ This is the production-default for a humanoid character that can move, attack, t
 - **Hit** same pattern, higher priority — interrupts attack. Fires on `damaged` signal.
 - **Dead** is a transition-target with no exit. Trigger via `state_machine.travel("dead")`.
 
+## The fast lane: script the wiring (preferred)
+
+Before walking the CRUD steps below, check the ctx lane — one `summer_run_script` call replaces the add-node/set-prop chain AND the hand-written `.tres`:
+
+- **Animation-tier engines:** `ctx.anim_state_machine(character, {states: {...}, transitions: [[from, to, {blend_s: 0.2}], ...], start: "idle"})` gets-or-creates the AnimationTree, wires it to the player, builds the state machine, sets `active = true`. Unknown clip names come back as a report entry listing the player's REAL clips — never wire against guessed names. Full recipe (inspect clips/bones first, method-track events, root motion, playtest verification): `character-animation-wiring`.
+- **Any engine (raw fallback):** the same classes are fully script-bound — `AnimationNodeStateMachine.add_node(name, AnimationNodeAnimation)`, `add_transition(from, to, AnimationNodeStateMachineTransition)` (one transition resource each, `xfade_time` on it), then `tree.anim_player = tree.get_path_to(player)`, `tree.tree_root = sm`, `tree.active = true`, and `ctx.set_owner_recursive(tree)`. The raw script is quoted in `character-animation-wiring`.
+
+Note the helper's scope honestly: `anim_state_machine` builds clip states + transitions only. The canonical machine below — BlendSpace1D locomotion, OneShot attack/hit — still needs the `.tres` (or raw-script) lane for those node types. Discrete idle/walk/run backbones don't.
+
 ## Steps via MCP
 
 ### 1. Inspect the current character
@@ -74,7 +83,7 @@ summer_get_scene_tree
 summer_inspect_node "./World/Goblin"
 ```
 
-Confirm there's a `Skeleton3D` and an `AnimationPlayer` with at least `idle` + `walk` + `run` populated. If clips are missing, route to `summer:animation/generate-motion`.
+Confirm there's a `Skeleton3D` and an `AnimationPlayer` with at least `idle` + `walk` + `run` populated. If clips are missing, route to `generate-motion`.
 
 ### 2. Add the AnimationTree
 
@@ -96,10 +105,15 @@ before it reaches the engine. Get the path from `summer_get_project_context`.
 
 The `tree_root` is a single `AnimationNodeStateMachine`. Inside it, a `Locomotion` node which is itself an `AnimationNodeBlendSpace1D`, plus `Attack`, `Hit`, `Dead` nodes.
 
-This is more readable to edit by hand or in Summer Engine, then commit the
-`.tres`. The MCP tool `summer_set_resource_property` can build it node-by-node,
-but the tree-resource model is verbose enough that **writing the `.tres` and
-importing it is faster** for the canonical structure. Skeleton:
+Three ways to build it, in preference order: (1) a `summer_run_script` GDScript
+constructing the node graph via the script-bound API — transactional, no
+hand-parsed text format (see the fast-lane section above; BlendSpace1D and
+OneShot nodes are `AnimationNodeBlendSpace1D.new()` + `add_blend_point(...)`
+and `AnimationNodeOneShot.new()` with `fadein_time`/`fadeout_time`, composed
+with the same `add_node`/`add_transition` calls); (2) hand-writing the `.tres`
+below and importing it; (3) `summer_set_resource_property` node-by-node — the
+most verbose, use only for touch-ups. The `.tres` skeleton, for the read/write
+fallback lane:
 
 ```
 [gd_resource type="AnimationNodeStateMachine" load_steps=8 format=3]
@@ -275,12 +289,13 @@ the same `.tres`; it is slower but discoverable.
 
 ## Handoff
 
-- For NPC behavior firing these states (decide-when-to-attack), hand off to `summer:ai-and-npcs/design-npc`.
-- For first-person hand animations on the player rig, the same pattern applies — hand off to `summer:character-controllers/fps-controller` for the state inputs.
-- For procedural overlays on top of the tree (look-at the player while idling), hand off to `summer:animation/procedural-animation`.
-- For lipsync layered on the face during dialogue states, hand off to `summer:animation/facial-and-lipsync`.
+- For NPC behavior firing these states (decide-when-to-attack), hand off to `design-npc`.
+- For first-person hand animations on the player rig, the same pattern applies — hand off to `fps-controller` for the state inputs.
+- For procedural overlays on top of the tree (look-at the player while idling), hand off to `procedural-animation`.
+- For lipsync layered on the face during dialogue states, hand off to `facial-and-lipsync`.
 
 ## See also
 
-- `summer:animation/generate-motion` — produce the clips this tree references.
-- `summer:animation/retarget` — share one tree across many characters.
+- `character-animation-wiring` — the end-to-end rigged-GLB path: inspect real clip/bone names, `ctx.anim_state_machine`, method tracks, root motion, playtest verification.
+- `generate-motion` — produce the clips this tree references.
+- `retarget` — share one tree across many characters.

package/library/skills/animation-tree/resource.yaml

@@ -0,0 +1,33 @@
+id: skill/animation-tree
+kind: skill
+version: 1.0.1
+summary: Design and wire AnimationTree state machines and blend trees so clips respond to gameplay — locomotion blends, attack interrupts, hit reactions.
+use_when:
+  - the character has clips that must play in response to gameplay — idle/walk/run blends, attacks that interrupt locomotion, hit reactions
+  - a character keeps T-posing
+facets:
+  lifecycle:
+    - build
+  domains:
+    - animation
+    - 3d
+  modalities:
+    - animation
+    - scenes
+compatibility:
+  engine: ">=4.6"
+related:
+  skills:
+    - skill/character-animation-wiring
+    - skill/design-npc
+    - skill/facial-and-lipsync
+    - skill/generate-motion
+    - skill/procedural-animation
+    - skill/retarget
+    - skill/fps-controller
+source: official
+license: MIT
+status: stable
+recommended: false
+aliases:
+  - skills/animation/animation-tree

package/{skills/rendering-and-lighting → library/skills}/art-direction/SKILL.md

@@ -244,8 +244,8 @@ Ask:
 End with:
 
 > Bible saved. Next:
-> - `/summer:audio-direction` to define the sonic identity that pairs with this look.
-> - `/summer:vfx` to design particle / hit-feedback styles within the palette.
+> - `/audio-direction` to define the sonic identity that pairs with this look.
+> - `/game-feel` to design particle / hit-feedback styles within the palette.
 > - Open the project's `WorldEnvironment` node and dial in the lighting plan.
 > - Or generate first-pass concept assets via `summer_generate_image` using the palette + mood as the prompt prefix.
 
@@ -270,7 +270,7 @@ This skill writes one design doc (`.summer/art-bible.md`) and may modify `projec
 
 ## Want a working starter?
 
-No template — this is a workflow that produces the bible the rest of the project obeys. After the bible exists, every `summer:` rendering / lighting / shader / VFX skill reads it.
+No template — this is a workflow that produces the bible the rest of the project obeys. After the bible exists, every Summer rendering / lighting / shader / VFX skill reads it.
 
 ## See also
 

package/library/skills/art-direction/resource.yaml

@@ -0,0 +1,29 @@
+id: skill/art-direction
+kind: skill
+version: 1.0.2
+summary: Define the game's visual style — references, palette, mood, lighting plan, post-processing, do/don't list — output as an art bible at .summer/art-bible.md.
+use_when:
+  - defining the visual style of the game — references, palette, mood, lighting plan, post-processing
+  - make it look like PS1, retro, low-poly, pixel art, cel-shaded, or a horror aesthetic
+  - define the visual style before making any assets
+facets:
+  lifecycle:
+    - build
+  domains:
+    - rendering
+    - lighting
+  modalities:
+    - docs
+compatibility:
+  engine: ">=4.6"
+related:
+  skills:
+    - skill/audio-direction
+    - skill/3d-lighting
+    - skill/brainstorm-game
+source: official
+license: MIT
+status: stable
+recommended: true
+aliases:
+  - skills/rendering-and-lighting/art-direction

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

@@ -31,12 +31,12 @@ Ask the **exact phrase** before dispatching. Skipping the question is the most c
 
 | Ambiguity | Disambiguation question (verbatim) | Routes |
 |---|---|---|
-| Concept art vs character portrait | "Quick check — exploring the look (3-4 variants for art direction) or generating a final character portrait for dialogue UI?" | `summer:2d-assets/concept-art` (exploring) / `summer:2d-assets/character-portrait` (final) |
-| Prop vs character model | "Static object (sword, chair, lantern) or rigged character that needs animation?" | `summer:3d-assets/prop-model` / `summer:3d-assets/character-model` |
-| Tile vs sprite sheet | "One seamless tile that repeats, or a frame grid for an animated sprite?" | `summer:2d-assets/tileable-texture` / `summer:2d-assets/sprite-sheet` |
-| SFX vs music | "One-shot effect or a longer track (loop, theme, ambient bed)?" | `summer:audio/sound-effect` / `summer:audio/music-track` (or `audio/ambient-bed`) |
-| Generate vs retarget motion | "Generate a new clip on this character, or apply an existing library to a new character?" | `summer:animation/generate-motion` / `summer:animation/retarget` |
-| VFX recipe vs game-feel | "Particle/shader effect in the world or screen-feel (camera shake, hit-stop)?" | `summer:visual-effects/recipes/<name>` / `summer:visual-effects/game-feel` |
+| Concept art vs character portrait | "Quick check — exploring the look (3-4 variants for art direction) or generating a final character portrait for dialogue UI?" | `concept-art` (exploring) / `character-portrait` (final) |
+| Prop vs character model | "Static object (sword, chair, lantern) or rigged character that needs animation?" | `prop-model` / `character-model` |
+| Tile vs sprite sheet | "One seamless tile that repeats, or a frame grid for an animated sprite?" | `tileable-texture` / `sprite-sheet` |
+| SFX vs music | "One-shot effect or a longer track (loop, theme, ambient bed)?" | `sound-effect` / `music-track` (or `audio/ambient-bed`) |
+| Generate vs retarget motion | "Generate a new clip on this character, or apply an existing library to a new character?" | `generate-motion` / `retarget` |
+| VFX recipe vs game-feel | "Particle/shader effect in the world or screen-feel (camera shake, hit-stop)?" | `vfx-<name>` / `game-feel` |
 
 ## Step 3 — Dispatch
 
@@ -48,23 +48,23 @@ Invoke the specialist via the `Skill` tool. Don't paraphrase — let it run. Pas
 
 | Request | Skill |
 |---|---|
-| Concept / mood board / variants | `summer:2d-assets/concept-art` |
-| Polished portrait / NPC bust | `summer:2d-assets/character-portrait` |
-| Pixel sprite / retro icon | `summer:2d-assets/pixel-art` |
-| HUD / button / inventory frame | `summer:2d-assets/ui-graphics` |
-| Wall / floor / seamless ground | `summer:2d-assets/tileable-texture` |
-| Run cycle / spritesheet grid | `summer:2d-assets/sprite-sheet` |
-| 360 sky / panoramic background | `summer:2d-assets/skybox-panorama` |
+| Concept / mood board / variants | `concept-art` |
+| Polished portrait / NPC bust | `character-portrait` |
+| Pixel sprite / retro icon | `pixel-art` |
+| HUD / button / inventory frame | `ui-graphics` |
+| Wall / floor / seamless ground | `tileable-texture` |
+| Run cycle / spritesheet grid | `sprite-sheet` |
+| 360 sky / panoramic background | `skybox-panorama` |
 
 ### 3D assets
 
 | Request | Skill |
 |---|---|
-| Sword / chair / barrel / static object | `summer:3d-assets/prop-model` |
-| Player / NPC / enemy / boss / rigged humanoid | `summer:3d-assets/character-model` (canonical Meshy auto-rig) |
-| Modular dungeon / building blocks | `summer:3d-assets/environment-kit` |
-| Car / spaceship / hard-surface vehicle | `summer:3d-assets/vehicle-model` |
-| Tree / rock / mushroom / foliage | `summer:3d-assets/organic-model` |
+| Sword / chair / barrel / static object | `prop-model` |
+| Player / NPC / enemy / boss / rigged humanoid | `character-model` (canonical Meshy auto-rig) |
+| Modular dungeon / building blocks | `environment-kit` |
+| Car / spaceship / hard-surface vehicle | `vehicle-model` |
+| Tree / rock / mushroom / foliage | `organic-model` |
 
 Polycount targets (hero 8k–15k, grunt 3k–6k, mobile 1k–3k, cinematic 20k–40k) live in each specialist.
 
@@ -72,30 +72,30 @@ Polycount targets (hero 8k–15k, grunt 3k–6k, mobile 1k–3k, cinematic 20k
 
 | Request | Skill |
 |---|---|
-| Sword clash / footstep / UI click | `summer:audio/sound-effect` |
-| Theme / level music / boss track | `summer:audio/music-track` |
-| Forest ambience / cave drone | `summer:audio/ambient-bed` |
-| NPC line / VO / spoken dialogue | `summer:audio/voice-line` |
-| Music that reacts to combat | `summer:audio/adaptive-music` |
-| What should this game sound like | `summer:audio/audio-direction` |
+| Sword clash / footstep / UI click | `sound-effect` |
+| Theme / level music / boss track | `music-track` |
+| Forest ambience / cave drone | `ambient-bed` |
+| NPC line / VO / spoken dialogue | `voice-line` |
+| Music that reacts to combat | `adaptive-music` |
+| What should this game sound like | `audio-direction` |
 
 ### Animation
 
 | Request | Skill |
 |---|---|
-| Idle / walk / run / attack — new clip | `summer:animation/generate-motion` |
-| Apply library to a different character | `summer:animation/retarget` |
-| Blend tree / state machine | `summer:animation/animation-tree` |
-| Look-at / IK / foot placement | `summer:animation/procedural-animation` |
-| Lipsync / facial blendshapes | `summer:animation/facial-and-lipsync` |
+| Idle / walk / run / attack — new clip | `generate-motion` |
+| Apply library to a different character | `retarget` |
+| Blend tree / state machine | `animation-tree` |
+| Look-at / IK / foot placement | `procedural-animation` |
+| Lipsync / facial blendshapes | `facial-and-lipsync` |
 
 ### Video
 
 | Request | Skill |
 |---|---|
-| Intro cutscene / story sequence | `summer:video/cinematic-cutscene` |
-| Steam trailer / marketing clip | `summer:video/trailer-shot` |
-| Animated menu background / loop | `summer:video/animated-loop` |
+| Intro cutscene / story sequence | `cinematic-cutscene` |
+| Steam trailer / marketing clip | `trailer-shot` |
+| Animated menu background / loop | `animated-loop` |
 
 ### Visual effects
 
@@ -103,23 +103,23 @@ VFX is **code, not generative** — recipes are shader + GDScript + node setup,
 
 | Request | Skill |
 |---|---|
-| Fire / torch / campfire | `summer:visual-effects/recipes/fire` |
-| Muzzle flash / gunshot | `summer:visual-effects/recipes/muzzle-flash` |
-| Water ripple / splash | `summer:visual-effects/recipes/water-ripple` |
-| Lightning / electric arc | `summer:visual-effects/recipes/lightning` |
-| Dissolve / disintegrate | `summer:visual-effects/recipes/dissolve` |
-| Smoke / dust puff | `summer:visual-effects/recipes/smoke` |
-| Hit spark / impact flash | `summer:visual-effects/recipes/hit-spark` |
-| Magic glow / aura | `summer:visual-effects/recipes/magic-glow` |
-| Camera shake / hit-stop | `summer:visual-effects/game-feel` |
+| Fire / torch / campfire | `vfx-fire` |
+| Muzzle flash / gunshot | `vfx-muzzle-flash` |
+| Water ripple / splash | `vfx-water-ripple` |
+| Lightning / electric arc | `vfx-lightning` |
+| Dissolve / disintegrate | `vfx-dissolve` |
+| Smoke / dust puff | `vfx-smoke` |
+| Hit spark / impact flash | `vfx-hit-spark` |
+| Magic glow / aura | `vfx-magic-glow` |
+| Camera shake / hit-stop | `game-feel` |
 
 ## When NOT to use this skill
 
 - The user already named the specific skill — go straight there.
-- The user is debugging or running the game — route to `summer:debug` or `summer:play`.
+- The user is debugging or running the game — route to `debug` or `play`.
 - The asset is an existing Summer asset ID — call `summer_get_asset`, then `summer_import_asset_by_id`.
 - The asset is being imported from a non-Summer URL (`.glb` / `.wav` from Sketchfab, Quaternius, AmbientCG) — call `summer_import_from_url` directly.
-- The user wants to plan the whole game's asset list — `summer:brainstorm-game` first, then this router on each item.
+- The user wants to plan the whole game's asset list — `brainstorm-game` first, then this router on each item.
 
 ## Anti-patterns
 
@@ -127,7 +127,7 @@ VFX is **code, not generative** — recipes are shader + GDScript + node setup,
 - **Skipping the disambiguation question.** Sends users to the wrong specialist and burns a paid generation. The verbatim phrasing in Step 2 is required.
 - **Routing concept-art to character-portrait** (or the reverse). Different goals: concept-art produces 4 divergent variants for art direction; character-portrait produces 1 polished bust for dialogue UI.
 - **Inventing skill names.** Only dispatch to skills listed above. If nothing fits, ask the user to clarify.
-- **Routing rigged-humanoid requests to `prop-model`.** Anything that needs animation always goes to `summer:3d-assets/character-model`.
+- **Routing rigged-humanoid requests to `prop-model`.** Anything that needs animation always goes to `character-model`.
 
 ## Fallback (no MCP)
 

package/library/skills/asset-strategy/resource.yaml

@@ -0,0 +1,63 @@
+id: skill/asset-strategy
+kind: skill
+version: 1.0.2
+summary: Route any 'I need a [thing]' asset request to the right specialist skill — disambiguates 2D / 3D / audio / video / VFX / animation pipelines.
+use_when:
+  - planning asset creation, picking an asset pipeline, or routing an 'I need a [thing]' request to the right specialist skill
+  - '"I need a sword / a forest / a boss theme / an explosion" and it is unclear which pipeline (2D, 3D, audio, video, VFX, animation) fits'
+  - deciding what to generate versus import from the library before a big content pass
+do_not_use_when:
+  - the pipeline is already obvious — go straight to the specialist skill (pixel-art, character-model, sound-effect, ...)
+facets:
+  lifecycle:
+    - build
+  domains:
+    - assets
+    - pipeline
+  modalities:
+    - assets
+compatibility:
+  engine: ">=4.6"
+related:
+  skills:
+    - skill/character-portrait
+    - skill/concept-art
+    - skill/pixel-art
+    - skill/skybox-panorama
+    - skill/sprite-sheet
+    - skill/tileable-texture
+    - skill/ui-graphics
+    - skill/character-model
+    - skill/environment-kit
+    - skill/organic-model
+    - skill/prop-model
+    - skill/vehicle-model
+    - skill/animation-tree
+    - skill/facial-and-lipsync
+    - skill/generate-motion
+    - skill/procedural-animation
+    - skill/retarget
+    - skill/adaptive-music
+    - skill/ambient-bed
+    - skill/audio-direction
+    - skill/music-track
+    - skill/sound-effect
+    - skill/voice-line
+    - skill/animated-loop
+    - skill/cinematic-cutscene
+    - skill/trailer-shot
+    - skill/game-feel
+    - skill/vfx-dissolve
+    - skill/vfx-fire
+    - skill/vfx-hit-spark
+    - skill/vfx-lightning
+    - skill/vfx-magic-glow
+    - skill/vfx-muzzle-flash
+    - skill/vfx-smoke
+    - skill/vfx-water-ripple
+source: official
+license: MIT
+status: stable
+recommended: true
+aliases:
+  - skills/asset-pipeline/asset-strategy

package/{skills/audio → library/skills}/audio-direction/SKILL.md

@@ -222,8 +222,8 @@ Ask first:
 End with:
 
 > Bible saved. Next:
-> - `/summer:design-mechanic` to wire SFX cues into specific mechanics.
-> - `/summer:vfx` if you haven't paired audio with visual effect cues yet.
+> - `/design-mechanic` to wire SFX cues into specific mechanics.
+> - `/game-feel` if you haven't paired audio with visual effect cues yet.
 > - Author or generate the calm music track first; it's the longest-running and sets the room tone.
 
 ## Common mistakes
@@ -239,11 +239,11 @@ End with:
 | Pure sine "ding" for pickup | Reads as cheap mobile game. Use a major-third interval with character. |
 | Same footstep sample for all surfaces | Material-aware footsteps are 80% of the perceived audio quality. |
 | No master ceiling / true peak | Audio clips on console builds without `-1 dBTP` ceiling. Always set it. |
-| Calling SetResourceProperty on inline sub_resources | Silent fail. See `../../../references/mcp-tools-reference.md` § Trap. |
+| Assuming SetResourceProperty fails silently on inline sub_resources | It does not — inline targets work, and the structural failures (`node not found`, `property is not a resource`, `resource is null`) are explicit errors. What *is* silent on current engines is a bad value shape: a JSON object instead of a Godot literal string, a misspelled `subProperty`, or a wrong-typed value returns `ok:true` yet no-ops or coerces destructively. Pass class names and literal strings, and confirm in the saved `.tres`/`.tscn`, never from `ok` alone. See `../../references/mcp-tools-reference/mcp-tools-reference.md`. |
 
 ## Collaborative protocol
 
-This skill writes one bible (`.summer/audio-bible.md`), creates a bus layout (`audio/default_bus_layout.tres`), modifies `project.godot`, and may generate audio (metered). Always ask before writing or generating. See `../../../references/collaborative-protocol.md`.
+This skill writes one bible (`.summer/audio-bible.md`), creates a bus layout (`audio/default_bus_layout.tres`), modifies `project.godot`, and may generate audio (metered). Always ask before writing or generating. See `../../references/collaborative-protocol/collaborative-protocol.md`.
 
 ## Want a working starter?
 
@@ -251,10 +251,10 @@ No template — this is a workflow that produces the bible the rest of the proje
 
 ## See also
 
-- `../../../references/collaborative-protocol.md`
-- `../../../references/godot-version.md` — Summer compatibility and
+- `../../references/collaborative-protocol/collaborative-protocol.md`
+- `../../references/godot-version/godot-version.md` — Summer compatibility and
   version-sensitive audio API notes
-- `../../../references/mcp-tools-reference.md`
+- `../../references/mcp-tools-reference/mcp-tools-reference.md`
 - `scene-and-project/brainstorm-game/SKILL.md` — produces the brief that anchors the bible
 - `rendering-and-lighting/art-direction/SKILL.md` — the visual counterpart; audio must rhyme with it
 - `audio/audio-bus-setup/SKILL.md` (NEXT) — implements the bus layout in detail

package/library/skills/audio-direction/resource.yaml

@@ -0,0 +1,32 @@
+id: skill/audio-direction
+kind: skill
+version: 1.0.6
+summary: Define the game's sonic identity — music style, instruments, SFX vocabulary, dynamic music plan — output as an audio bible at .summer/audio-bible.md.
+use_when:
+  - defining the sonic identity — music style, instruments, SFX vocabulary, dynamic music plan
+  - starting audio work with no audio bible, or soundtrack and SFX requests keep drifting in style
+  - '"what should my game sound like overall?" / "what is the audio vibe of this game?" — the whole-game sound question, before any single track or effect is made'
+facets:
+  lifecycle:
+    - build
+  domains:
+    - audio
+    - game-design
+  modalities:
+    - audio
+    - docs
+compatibility:
+  engine: ">=4.6"
+related:
+  skills:
+    - skill/art-direction
+    - skill/brainstorm-game
+    - skill/adaptive-music
+    - skill/music-track
+    - skill/sound-effect
+source: official
+license: MIT
+status: stable
+recommended: true
+aliases:
+  - skills/audio/audio-direction

package/library/skills/auto-fire-targeting/resource.yaml

@@ -0,0 +1,22 @@
+id: skill/auto-fire-targeting
+kind: skill
+version: 1.0.0
+summary: Design or fix auto-fire weapon targeting (survivors, top-down ARPG, tower defense) — the pending-damage pattern that prevents over-commit and overkill.
+use_when:
+  - designing or fixing the targeting system for an auto-fire weapon (survivors-genre, top-down ARPG, tower-defense)
+  - bullet flight time longer than fire rate causes wasted bullets or overkill
+facets:
+  lifecycle:
+    - build
+  domains:
+    - gameplay
+    - game-design
+  modalities:
+    - scripts
+compatibility:
+  engine: ">=4.6"
+source: official
+license: MIT
+status: stable
+aliases:
+  - skills/gameplay-mechanics/auto-fire-targeting

package/{skills/scene-and-project → library/skills}/brainstorm-game/SKILL.md

@@ -13,7 +13,7 @@ paths: [".summer/**", "project.godot", "**/*.md"]
 
 ## Overview
 
-Most game projects fail because they were never scoped. This skill turns "I want to make a game" into a 1-page brief that names the pitch, the core loop, three mechanics max, the art direction, and the scope (jam / vertical slice / full game). The brief lands at `.summer/GameSoul.md` — the file Summer's onboarding pipeline and every future `summer:` skill reads on first turn.
+Most game projects fail because they were never scoped. This skill turns "I want to make a game" into a 1-page brief that names the pitch, the core loop, three mechanics max, the art direction, and the scope (jam / vertical slice / full game). The brief lands at `.summer/GameSoul.md` — the file Summer's onboarding pipeline and every future Summer skill reads on first turn.
 
 **Core principle:** Constrain ruthlessly. A buildable bad idea beats an un-buildable great idea. Three mechanics, one art direction, one scope. Anything else gets parked in a "Later" list.
 
@@ -93,7 +93,7 @@ Ask:
 
 > One phrase for the look. If a stranger asked your screenshot's style in 6 words, what do you say?
 
-Don't go deeper here — `/summer:art-direction` is where the bible gets built. This is one phrase to seed it.
+Don't go deeper here — `/art-direction` is where the bible gets built. This is one phrase to seed it.
 
 ### 6. Pin the scope
 
@@ -171,10 +171,10 @@ Print the full brief to the user with the explicit instruction:
 End every successful brainstorm with a routing question:
 
 > Brief saved. Next step:
-> - `/summer:design-mechanic` — design the core loop in detail (recommended for vertical slice).
-> - `/summer:design-level` — sketch level 1 / the tutorial.
-> - `/summer:art-direction` — turn the one-phrase look into an art bible.
-> - Or pick up `/summer:make-game` to start scaffolding the project.
+> - `/design-mechanic` — design the core loop in detail (recommended for vertical slice).
+> - `/design-level` — sketch level 1 / the tutorial.
+> - `/art-direction` — turn the one-phrase look into an art bible.
+> - Or pick up `/make-game` to start scaffolding the project.
 
 Don't auto-pick. Let them decide.
 
@@ -188,7 +188,7 @@ Don't auto-pick. Let them decide.
 | Writing the brief without showing it first | They have to react to it. They'll catch their own bad fits when they read it back. |
 | Defaulting to "full game" scope | New devs overestimate. Default to vertical slice; let them upgrade if they push. |
 | Pitching a genre they didn't ask for | The first sentence they typed is signal. Don't override it. |
-| Including art direction details | One phrase. Bible-building is `/summer:art-direction`. |
+| Including art direction details | One phrase. Bible-building is `/art-direction`. |
 | Saving without asking | Always ask "May I create `.summer/GameSoul.md`?" — see collaborative-protocol. |
 
 ## Collaborative protocol
@@ -197,7 +197,7 @@ This skill writes one file (`.summer/GameSoul.md`). Always ask before writing. A
 
 ## Want a working starter?
 
-No template — this is a workflow that produces the brief that drives template selection later. Once `.summer/GameSoul.md` exists, `/summer:make-game` reads it and `summer list templates` shows what's actually available to match against.
+No template — this is a workflow that produces the brief that drives template selection later. Once `.summer/GameSoul.md` exists, `/make-game` reads it and `summer list templates` shows what's actually available to match against.
 
 ## See also