summer-engine 2.8.2 → 3.0.0

package/library/skills/skintokens-auto-rigging/resource.yaml

@@ -0,0 +1,38 @@
+id: skill/skintokens-auto-rigging
+kind: skill
+version: 0.1.1
+summary: "Offline auto-rigging with skin-tokens.cpp (GGML SkinTokens/TokenRig port) — skeleton and skin weights from a static GLB mesh on CPU/Vulkan, into Godot 4."
+use_when:
+  - "auto-rig this static GLB mesh so I can animate it"
+  - "generate skin weights for a mesh that already has a skeleton"
+  - "batch-rig many creature or character meshes without hand-painting weights"
+  - "I have an unrigged AI-generated character and need a first-pass rig"
+do_not_use_when:
+  - "hero characters needing art-directed deformation, non-triangle meshes, shapes far from the humanoid training data, or runtime in-engine rigging"
+  - "skin-tokens.cpp is a user-built, user-run offline CLI (minutes per mesh); the agent does not install or run it on the user's behalf"
+  - "intake from the gamedev-knowledge pipeline (source-cited, pipeline-validated, not yet exercised in-engine by the Summer team) — verify results in the engine as you would any technique"
+facets:
+  lifecycle:
+    - build
+  domains:
+    - assets
+    - pipeline
+    - 3d
+    - animation
+  modalities:
+    - 3d-models
+    - assets
+compatibility:
+  engine: ">=4.6"
+related:
+  skills:
+    - skill/character-model
+    - skill/retarget
+source: official
+license: MIT
+status: preview
+recommended: false
+lint_exceptions:
+  - url-allowlist
+  - credential-pattern
+lint_exception_reason: "Source citation for knowledge extracted by the gamedev-knowledge pipeline: the Setup section quotes the upstream GitHub clone URL of the skin-tokens.cpp tool (localai-org) as a user-run, user-consented build step — a read-only provenance link, not agent-autonomous installation. credential-pattern is a false positive on the CMake option SKINTOKENS_ENABLE_VULKAN, where TOKENS is part of the project name, not a secret or token assignment."

package/{skills/2d-assets → library/skills}/skybox-panorama/SKILL.md

@@ -188,15 +188,15 @@ If MCP is offline entirely: Polyhaven (`polyhaven.com/hdris`) has hundreds of fr
 
 After the sky is wired:
 
-- **Add atmospheric fog matching the sky's mood** → `summer:scene-composition` (fog is on the same Environment resource).
-- **Add a directional `DirectionalLight3D` matching the sun position in the panorama** → `summer:3d-lighting` for sun + shadows.
+- **Add atmospheric fog matching the sky's mood** → `scene-composition` (fog is on the same Environment resource).
+- **Add a directional `DirectionalLight3D` matching the sun position in the panorama** → `3d-lighting` for sun + shadows.
 - **Day/night cycle** → re-invoke this skill for the night sky, then write a small tween between the two `panorama` properties.
-- **Tileable ground texture for the level floor** → `summer:2d-assets/tileable-texture`.
+- **Tileable ground texture for the level floor** → `tileable-texture`.
 
 ## See also
 
-- `summer:3d-lighting` — sun, ambient, fog wired alongside the sky.
-- `summer:2d-assets/tileable-texture` — ground/floor counterpart.
-- `summer:scene-composition` — WorldEnvironment placement and configuration.
-- `summer:asset-pipeline/asset-strategy` — meta-router.
-- `../../../references/mcp-tools-reference.md` — `summer_generate_image` schema.
+- `3d-lighting` — sun, ambient, fog wired alongside the sky.
+- `tileable-texture` — ground/floor counterpart.
+- `scene-composition` — WorldEnvironment placement and configuration.
+- `asset-strategy` — meta-router.
+- `../../references/mcp-tools-reference/mcp-tools-reference.md` — `summer_generate_image` schema.

package/library/skills/skybox-panorama/resource.yaml

@@ -0,0 +1,28 @@
+id: skill/skybox-panorama
+kind: skill
+version: 1.0.3
+summary: Generate a 360-degree equirectangular sky panorama and wire it as a PanoramaSkyMaterial Sky resource on WorldEnvironment in a 3D scene.
+use_when:
+  - generating a 360-degree panoramic sky image for use as a Sky resource (PanoramaSkyMaterial) in a 3D scene
+  - a 3D scene has a flat or default sky and needs a 360-degree backdrop matching the art direction
+facets:
+  lifecycle:
+    - build
+  domains:
+    - 2d
+    - assets
+  modalities:
+    - images
+    - scenes
+compatibility:
+  engine: ">=4.6"
+related:
+  skills:
+    - skill/tileable-texture
+    - skill/asset-strategy
+source: official
+license: MIT
+status: stable
+recommended: false
+aliases:
+  - skills/2d-assets/skybox-panorama

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

@@ -238,5 +238,5 @@ After the SFX is wired:
 - `audio/ambient-bed` — long looping textures
 - `audio/music-track` — music
 - `audio/voice-line` — TTS
-- `../../../references/mcp-tools-reference.md`
-- `../../../references/godot-version.md` — Summer compatibility for audio nodes
+- `../../references/mcp-tools-reference/mcp-tools-reference.md`
+- `../../references/godot-version/godot-version.md` — Summer compatibility for audio nodes

package/library/skills/sound-effect/resource.yaml

@@ -0,0 +1,27 @@
+id: skill/sound-effect
+kind: skill
+version: 1.0.3
+summary: Generate short SFX one-shots — footsteps, weapon swings, UI clicks, hit impacts — wired as AudioStreamPlayer/2D/3D that auto-frees on finished.
+use_when:
+  - generating short SFX one-shots — footsteps, weapon swings, UI clicks, hit impacts, environmental cues
+  - an action, impact, or UI interaction is silent and needs a short one-shot sound wired to it
+facets:
+  lifecycle:
+    - build
+  domains:
+    - audio
+    - assets
+  modalities:
+    - audio
+    - scenes
+compatibility:
+  engine: ">=4.6"
+related:
+  skills:
+    - skill/audio-direction
+source: official
+license: MIT
+status: stable
+recommended: true
+aliases:
+  - skills/audio/sound-effect

package/library/skills/spatial-placement/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: spatial-placement
+description: Use when positioning or verifying 3D objects with surrounding-scene evidence — floor and shelf support, wall gaps, collider or mesh overlap, directional clearance, alcoves, rotated props, and post-placement checks. Trigger on "place", "position", "align", "sit on", "against the wall", "inside", "overlap", "clearance", "grounded", "flush", "spatial", "Starcast".
+license: MIT
+compatibility: [Cursor, Claude Code, Windsurf, Codex]
+category: scene-and-project
+user-invocable: false
+allowed-tools: Read Grep summer_get_scene_tree summer_inspect_node summer_set_prop summer_batch summer_starcast
+paths: ["**/*.tscn"]
+---
+
+# Spatial Placement in Summer Engine
+
+Use Starcast as spatial evidence, not as an automatic placement solver. Make a
+reasonable transform from scene intent, inspect the result, then correct only
+the axes that the evidence shows are wrong.
+
+## Placement loop
+
+1. Call `summer_get_scene_tree` and inspect the subject and intended anchor.
+   Never guess paths, transforms, or dimensions.
+2. Place the subject approximately with `summer_set_prop` or `summer_batch`.
+3. Call `summer_starcast(scenePath, path, detail="summary")`.
+4. Correct position or rotation from the smallest relevant set of facts.
+5. Call summary again. Stop when the intended support/contact and clearances are
+   satisfied. Do not keep recasting a placement that already meets the brief.
+
+Use `detail="full"` only when summary identifies an ambiguous blocker, several
+nearby candidates, or a complex overlap. Full output is capped at 12 KB and may
+return summary automatically. Keep `directionSpace="world"` unless placement is
+defined relative to a rotated subject; then use `directionSpace="local"`.
+
+## Read the result
+
+- `subject.position` and `subject.size` describe the queried object.
+- `grounded: true` means downward support was detected. It does not mean the
+  object is centered or otherwise well placed.
+- `contactStatus` and `contacts` identify touching or overlapping colliders.
+  Godot's shape query cannot distinguish touching from penetration here.
+- `directions.<label>.status` is `blocked` when clearance is below the tool's
+  threshold; `distance` is measured from the subject bounds.
+- `evidence: "physics"` is exact collider-query evidence.
+- `evidence: "visual_aabb"` includes visible meshes without colliders, but is a
+  world-axis-aligned broad-phase approximation. Do not infer exact surface
+  contact from it.
+- Warnings about missing collision shapes or visual bounds mean coverage is
+  partial; state that limitation rather than inventing certainty.
+
+## Placement recipes
+
+- **Floor/platform:** require downward support, no unintended contacts, and open
+  movement/access directions. Correct vertical position first.
+- **Shelf:** require shelf support, no back/side overlap, and enough forward
+  clearance to remain visible and reachable.
+- **Wall:** use the intended horizontal direction as the anchor, preserve a
+  small gap unless contact is requested, and verify the opposite side is open.
+- **Alcove:** check back, both sides, up, down, and relevant diagonals. Request
+  full only if summary cannot identify which surface blocks the subject.
+- **Rotated object:** use local directions only when "front", "side", or "up"
+  refers to the object's orientation; use world directions for level axes.
+- **Overlap repair:** move along the clearest axis with the shortest correction,
+  then rerun. Do not resize the asset unless the user asked for that.
+
+## Guardrails
+
+- Always provide exact `scenePath` and `path`; selection fallback is not
+  deterministic agent behavior.
+- Starcast is read-only and never moves or saves the subject.
+- One representative ray per direction can miss off-center geometry. Combine
+  directional results with contacts, nearby evidence, hierarchy, and rendered
+  verification for high-consequence placements.
+- Cameras, lights, audio, navigation nodes, scripts, and plain Nodes are not
+  obstacles unless they own collision or renderable geometry.
+- Prefer two useful summary calls around one correction over repeated full calls.

package/library/skills/spatial-placement/resource.yaml

@@ -0,0 +1,42 @@
+id: skill/spatial-placement
+kind: skill
+version: 1.0.1
+summary: Place and verify 3D objects with Starcast evidence — inspect, place, starcast, correct, verify; floor, shelf, wall, alcove recipes and overlap repair.
+use_when:
+  - positioning a prop, character, collider, or platform so it sits flush, avoids overlap, or keeps clearance
+  - placing something against a wall, inside an alcove, or on a shelf and needing to know which side is blocked and by how much
+  - repairing an overlap or a floating object after a placement
+  - post-placement checks on a rotated prop using its own local axes
+do_not_use_when:
+  - the scene is 2D — Starcast reads Node3D bounds, 3D physics, and visual AABBs
+  - you want the engine to seat or align for you — skill/world-building-3d (summer_snap_to_surface, summer_align_distribute_3d)
+  - "the engine build predates Starcast3D (Summer Engine 0.5.66 or newer): summer_starcast returns engine_lacks_op; judge placement from summer_test_placement and summer_inspect_node instead"
+facets:
+  lifecycle:
+    - build
+  domains:
+    - scenes
+    - 3d
+    - world-building
+    - level-design
+    - verification
+  modalities:
+    - scenes
+compatibility:
+  engine: ">=4.6"
+related:
+  tools:
+    - tool/starcast
+    - tool/get-scene-tree
+    - tool/inspect-node
+    - tool/set-prop
+    - tool/batch
+  skills:
+    - skill/world-building-3d
+    - skill/scene-composition
+source: official
+license: MIT
+status: preview
+recommended: true
+aliases:
+  - skills/scene-and-project/spatial-placement

package/library/skills/spatial-placement/tests/spec.md

@@ -0,0 +1,65 @@
+# Skill Spec: /spatial-placement
+
+## Fixture
+
+- A 3D scene with a floor, a shelf unit with a back panel, a wall, a rotated
+  crate prop that owns a collider, and one visible mesh-only obstacle without
+  a collider.
+- `summer_starcast` is available on an engine build with `Starcast3D`, plus
+  `summer_get_scene_tree`, `summer_inspect_node`, `summer_set_prop`, and
+  `summer_batch`.
+
+## Case 1: Rotated prop on a shelf
+
+**Input:** "Put the crate on the middle shelf, flush against the back panel but
+not clipping it."
+
+**Expected MCP tool sequence (in order):**
+
+1. `summer_get_scene_tree`
+2. `summer_inspect_node` for the crate and the shelf
+3. `summer_set_prop` (approximate placement from scene intent)
+4. `summer_starcast` with `detail="summary"`
+5. `summer_set_prop` (one correction on only the axes the evidence names)
+6. `summer_starcast` with `detail="summary"`
+
+**Assertions:**
+
+- [ ] Every `summer_starcast` call passes exact `scenePath` and `path`; no
+  editor-selection fallback.
+- [ ] `grounded: true` with the shelf as the downward object; `contactStatus`
+  shows no unintended `contact_or_overlap`.
+- [ ] The back direction reports `blocked` at a small positive distance (or the
+  requested contact); the forward direction is `open`.
+- [ ] `directionSpace="local"` is used only because the crate is rotated;
+  `world` otherwise.
+- [ ] At most two summary calls around one correction; `detail="full"` is not
+  requested unless summary was ambiguous.
+
+## Case 2: Overlap repair with partial coverage
+
+**Input:** "The barrel is clipping into the wall, fix it."
+
+**Expected MCP tool sequence (in order):**
+
+1. `summer_starcast` with `detail="summary"`
+2. `summer_set_prop` along the clearest axis with the shortest correction
+3. `summer_starcast` with `detail="summary"`
+
+**Assertions:**
+
+- [ ] The correction moves along one axis only and does not resize the asset.
+- [ ] A `subject_has_no_collision_shapes` or `physics_unavailable` warning is
+  reported to the user as partial coverage, never silently ignored.
+- [ ] `evidence: "visual_aabb"` is never described as exact contact.
+
+## Case 3: Engine without Starcast3D
+
+**Input:** Case 1 on an engine build that predates `Starcast3D`.
+
+**Assertions:**
+
+- [ ] `summer_starcast` returns `failure_reason: engine_lacks_op`; the agent
+  does not retry blindly.
+- [ ] The agent falls back to `summer_test_placement` and `summer_inspect_node`
+  evidence and states which evidence it used.

package/{skills/2d-assets → library/skills}/sprite-sheet/SKILL.md

@@ -35,8 +35,8 @@ So do not tell the user to cut a generated sheet by hand or in ImageMagick. The
 
 ## When NOT to use
 
-- The character is 3D — use `summer:animation/generate-motion` for skeletal animation.
-- The user wants a single static sprite → `summer:2d-assets/pixel-art` or `summer:2d-assets/character-portrait`.
+- The character is 3D — use `generate-motion` for skeletal animation.
+- The user wants a single static sprite → `pixel-art` or `character-portrait`.
 - The user wants UI animation (loading spinner, button hover) — animate via `AnimationPlayer` rotating/tweening a static texture instead. Don't sprite-sheet UI.
 - The user has 12+ frames per animation and 4+ animations — that's hundreds of generations at $0.02 each. Pause and discuss budget.
 
@@ -47,7 +47,7 @@ So do not tell the user to cut a generated sheet by hand or in ImageMagick. The
 You need a stable reference. Either:
 
 - The user has a static sprite already (`res://sprites/goblin.png`) — use it as `referenceImageUrl`.
-- Generate a base sprite via `summer:2d-assets/pixel-art` or `summer:2d-assets/character-portrait` first, then return here.
+- Generate a base sprite via `pixel-art` or `character-portrait` first, then return here.
 
 Without a base, every frame drifts.
 
@@ -115,7 +115,7 @@ Tell the user:
 
 > AI sprite-sheet generation is unreliable — best path for clean pixel animation is to hand-author in Aseprite (or Piskel for free in-browser). Onion-skin frame-by-frame; ~10 minutes for a 4-frame walk cycle. Want me to generate a base reference image you can trace?
 
-If yes, generate the static base via `summer:2d-assets/pixel-art` and stop here. The user takes it to Aseprite.
+If yes, generate the static base via `pixel-art` and stop here. The user takes it to Aseprite.
 
 ### 4. Import frames into Summer Engine
 
@@ -230,15 +230,15 @@ Tell the user to run via the Summer dashboard. Or recommend Aseprite (paid, $20)
 After the animation is wired:
 
 - **More animations on the same character** (idle, attack, death) → re-invoke this skill with the same base anchor, vary the delta.
-- **Sound effects synced to animation frames** → `summer:audio/sound-effect`, then wire via `Call Method Track` in `AnimationPlayer`.
+- **Sound effects synced to animation frames** → `sound-effect`, then wire via `Call Method Track` in `AnimationPlayer`.
 - **Multi-direction sprites** → re-invoke per direction (budget warning).
-- **Pixel-art static base if not yet generated** → `summer:2d-assets/pixel-art` first.
-- **3D character animation instead** → `summer:animation/generate-motion`.
+- **Pixel-art static base if not yet generated** → `pixel-art` first.
+- **3D character animation instead** → `generate-motion`.
 
 ## See also
 
-- `summer:2d-assets/pixel-art` — base sprite generation.
-- `summer:2d-assets/character-portrait` — base portrait for higher-res characters.
-- `summer:animation/generate-motion` — 3D-skeletal counterpart.
-- `summer:audio/sound-effect` — frame-synced SFX.
-- `../../../references/mcp-tools-reference.md` — `summer_generate_image` schema.
+- `pixel-art` — base sprite generation.
+- `character-portrait` — base portrait for higher-res characters.
+- `generate-motion` — 3D-skeletal counterpart.
+- `sound-effect` — frame-synced SFX.
+- `../../references/mcp-tools-reference/mcp-tools-reference.md` — `summer_generate_image` schema.

package/library/skills/sprite-sheet/resource.yaml

@@ -0,0 +1,32 @@
+id: skill/sprite-sheet
+kind: skill
+version: 1.0.4
+summary: Generate animated 2D character sprites laid out as a sprite sheet — walk cycle, attack, idle, death — wired into AnimatedSprite2D / SpriteFrames.
+use_when:
+  - generating animated 2D character sprites laid out as a grid of frames — walk cycle, attack frames, idle bob, death sequence
+  - a 2D sprite needs its frames laid out as one grid image for AnimatedSprite2D or SpriteFrames
+facets:
+  lifecycle:
+    - build
+  domains:
+    - 2d
+    - assets
+  modalities:
+    - images
+    - assets
+compatibility:
+  engine: ">=4.6"
+related:
+  skills:
+    - skill/character-portrait
+    - skill/pixel-art
+    - skill/generate-motion
+    - skill/sound-effect
+    - skill/create-asset-sheet
+    - skill/asset-strategy
+source: official
+license: MIT
+status: stable
+recommended: false
+aliases:
+  - skills/2d-assets/sprite-sheet

package/{skills/2d-assets → library/skills}/tileable-texture/SKILL.md

@@ -25,9 +25,9 @@ The hard part is "seamless." Most diffusion models violate edge continuity by de
 
 ## When NOT to use
 
-- The user wants a 3D-modeled wall with geometric brick relief → `summer:asset-pipeline/asset-strategy` (image-to-3D).
-- The user wants a unique mural / non-tiling artwork → `summer:2d-assets/concept-art` or `summer:2d-assets/character-portrait`.
-- The user wants a skybox / 360° environment → `summer:2d-assets/skybox-panorama`.
+- The user wants a 3D-modeled wall with geometric brick relief → `asset-strategy` (image-to-3D).
+- The user wants a unique mural / non-tiling artwork → `concept-art` or `character-portrait`.
+- The user wants a skybox / 360° environment → `skybox-panorama`.
 - The user wants a normal map / PBR material set — generation today is albedo-only. Normals must be derived (`MaterialMaker`, `NormalMap-Online`) or hand-authored.
 
 ## Steps
@@ -199,13 +199,13 @@ If MCP is offline entirely: AmbientCG and Polyhaven offer free CC0 PBR texture s
 After the texture is wired:
 
 - **More textures in the same biome** → re-invoke this skill, hold style/lighting consistent.
-- **Apply to a procedurally-built level** → `summer:scene-composition` for CSG and modular wall kits.
+- **Apply to a procedurally-built level** → `scene-composition` for CSG and modular wall kits.
 - **PBR set with normals/roughness** → out of MCP scope today; user runs derivation in MaterialMaker.
-- **Skybox for the level's environment** → `summer:2d-assets/skybox-panorama`.
+- **Skybox for the level's environment** → `skybox-panorama`.
 
 ## See also
 
-- `summer:asset-pipeline/asset-strategy` — meta-router and 3D pipeline.
-- `summer:2d-assets/skybox-panorama` — sky/environment counterpart.
-- `summer:scene-composition` — applying textures to CSG and MeshInstance3D.
-- `../../../references/mcp-tools-reference.md` — `summer_generate_image` schema.
+- `asset-strategy` — meta-router and 3D pipeline.
+- `skybox-panorama` — sky/environment counterpart.
+- `scene-composition` — applying textures to CSG and MeshInstance3D.
+- `../../references/mcp-tools-reference/mcp-tools-reference.md` — `summer_generate_image` schema.

package/library/skills/tileable-texture/resource.yaml

@@ -0,0 +1,31 @@
+id: skill/tileable-texture
+kind: skill
+version: 1.0.4
+summary: Generate a seamless tileable texture for walls, floors, or terrain — repeats cleanly on all four edges, wired as a StandardMaterial3D albedo.
+use_when:
+  - generating a seamless tileable texture for walls, floors, terrain, or ceilings — a square tile that repeats cleanly on all four edges
+  - a wall, floor, or terrain material shows visible seams or repetition and needs a texture that tiles cleanly
+facets:
+  lifecycle:
+    - build
+  domains:
+    - 2d
+    - assets
+  modalities:
+    - images
+    - assets
+compatibility:
+  engine: ">=4.6"
+related:
+  skills:
+    - skill/character-portrait
+    - skill/concept-art
+    - skill/skybox-panorama
+    - skill/asset-strategy
+    - skill/create-asset-sheet
+source: official
+license: MIT
+status: stable
+recommended: false
+aliases:
+  - skills/2d-assets/tileable-texture

package/{skills/video → library/skills}/trailer-shot/SKILL.md

@@ -209,4 +209,4 @@ Once the shots are generated:
 - `audio/music-track` — trailer score.
 - `audio/sound-effect` — cut SFX (whooshes, impacts, stingers).
 - `2d-assets/concept-art` — generate the reference image axis when no asset exists yet.
-- `../../../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/trailer-shot/resource.yaml

@@ -0,0 +1,27 @@
+id: skill/trailer-shot
+kind: skill
+version: 1.0.4
+summary: Generate marketing or trailer footage — slow-mo combat, establishing shots, hero beats, splash screens, pitch-deck B-roll — max punch in 5-10 seconds.
+use_when:
+  - generating marketing or trailer footage — slow-mo combat, dramatic establishing shots, hero beats, splash screens, pitch-deck B-roll
+  - producing a store page, pitch deck, or social clip that shows the game at its most dramatic in seconds
+facets:
+  lifecycle:
+    - launch
+  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/trailer-shot

package/{skills/performance → library/skills}/tune-performance/SKILL.md

@@ -109,7 +109,7 @@ summer_inspect_node "./World/Enemy"
 summer_inspect_resource "./World/Enemy"   # for mesh/material/shape details
 ```
 
-**Bakes you cannot run for the user.** `LightmapGI` bake and the `OccluderInstance3D` bake are editor-process operations — `LightmapGI.bake()` is not exposed to scripting at all, and there is no MCP op for either. You can add and configure the nodes, but the bake itself is a button the user presses in the editor. Say so explicitly rather than reporting the optimization as applied. Navmesh baking, collision-shape generation from meshes, and `ImporterMesh.generate_lods` are all scriptable and remain yours to do.
+**Bakes: know which process can run them.** `LightmapGI.bake(from_node, image_data_path)` IS script-bound on this build — run it from `summer_run_script` in the live editor (the GPU lightmapper needs a real renderer: desktop editors have one, cloud containers need xvfb + GL per `running-in-the-cloud`, and pure-headless returns `BAKE_ERROR_NO_LIGHTMAPPER`). The `OccluderInstance3D` bake remains editor-button only — say so rather than reporting it as applied. Navmesh baking, collision-shape generation from meshes, and `ImporterMesh.generate_lods` are all scriptable and remain yours to do.
 
 ### 4b. Physics hotspot
 
@@ -221,7 +221,7 @@ Compare: was the metric movement at least 50% of what was promised? If yes, ship
 
 ## Collaborative protocol
 
-This skill makes scene/resource/code changes. Always ask before each fix is applied. See `../../../references/collaborative-protocol.md`.
+This skill makes scene/resource/code changes. Always ask before each fix is applied. See `../../references/collaborative-protocol/collaborative-protocol.md`.
 
 ## Want a working starter?
 
@@ -229,10 +229,10 @@ No template — this is a workflow. Performance tuning is project-specific by de
 
 ## See also
 
-- `../../../references/mcp-tools-reference.md` — full MCP tool list
-- `../../../references/godot-version.md` — renderer API churn notes (Compositor, RenderSceneBuffers)
-- `../../../references/collaborative-protocol.md` — "May I write" pattern
-- `../../../references/gd-style.md` — GDScript conventions (avoid bare types, use `:=`)
+- `../../references/mcp-tools-reference/mcp-tools-reference.md` — full MCP tool list
+- `../../references/godot-version/godot-version.md` — renderer API churn notes (Compositor, RenderSceneBuffers)
+- `../../references/collaborative-protocol/collaborative-protocol.md` — "May I write" pattern
+- `../../references/gd-style/gd-style.md` — GDScript conventions (avoid bare types, use `:=`)
 - `debugging/debug/SKILL.md` — bug triage (related but different)
 - `workflow/diagnosing-perf-regressions/SKILL.md` — when it *got* slow rather than always was
 - `rendering-and-lighting/3d-lighting/SKILL.md` — light setup and bake decisions

package/library/skills/tune-performance/resource.yaml

@@ -0,0 +1,31 @@
+id: skill/tune-performance
+kind: skill
+version: 1.0.3
+summary: Profile a slow game via summer_get_diagnostics, identify rendering/physics/scripting hotspots, propose fixes with before/after metric expectations.
+use_when:
+  - the game is slow, drops framerate, stutters, takes forever to start, or runs poorly on specific hardware
+  - fps drops or stutter when many units, projectiles, or particles spawn at once and the hotspot is unknown
+facets:
+  lifecycle:
+    - build
+  domains:
+    - performance
+    - debug
+  modalities:
+    - scripts
+    - scenes
+compatibility:
+  engine: ">=4.6"
+related:
+  skills:
+    - skill/running-in-the-cloud
+    - skill/scene-scripting
+    - skill/debug
+    - skill/3d-lighting
+    - skill/diagnosing-perf-regressions
+source: official
+license: MIT
+status: stable
+recommended: true
+aliases:
+  - skills/performance/tune-performance

package/library/skills/ui-basics/resource.yaml

@@ -0,0 +1,25 @@
+id: skill/ui-basics
+kind: skill
+version: 1.0.3
+summary: Build Summer Engine UI — HUDs, menus, health bars, dialogue boxes, Control trees — anchors, containers, responsive layout, theme vs inline styling.
+use_when:
+  - "building Summer Engine UI: HUDs, main menus, pause menus, health bars, progress bars, dialogue boxes, or any Control-node tree"
+  - laying out a pause menu, settings screen, or inventory panel with anchors and containers so it stays responsive
+  - '"add a pause menu" / "add a settings screen" / "add an options menu" / "add a main menu"'
+facets:
+  lifecycle:
+    - build
+  domains:
+    - ui
+    - ux
+  modalities:
+    - ui
+    - scenes
+compatibility:
+  engine: ">=4.6"
+source: official
+license: MIT
+status: stable
+recommended: true
+aliases:
+  - skills/ui-and-ux/ui-basics

package/{skills/2d-assets → library/skills}/ui-graphics/SKILL.md

@@ -27,9 +27,9 @@ UI graphics succeed or fail on **two specific things**: a clean transparent back
 
 ## When NOT to use
 
-- The user wants a character portrait → `summer:2d-assets/character-portrait`.
-- The user wants pixel-art UI → `summer:2d-assets/pixel-art` (UI in pixel style needs a different prompt pattern).
-- The user wants a 3D HUD element → that's a 3D mesh job; route to `summer:asset-pipeline/asset-strategy`.
+- The user wants a character portrait → `character-portrait`.
+- The user wants pixel-art UI → `pixel-art` (UI in pixel style needs a different prompt pattern).
+- The user wants a 3D HUD element → that's a 3D mesh job; route to `asset-strategy`.
 - The user wants a font → fonts aren't generated; use a `.ttf`/`.otf` and import via `FontFile`.
 
 ## Steps
@@ -185,7 +185,7 @@ If you generate a 4×4 grid of icons in one image, each icon becomes an `AtlasTe
 - **User wants the same icon at multiple sizes (32, 64, 128).** Generate once
   at high resolution. Summer Engine's `TextureRect` with
   `STRETCH_KEEP_ASPECT_CENTERED` scales it down cleanly.
-- **User wants pixel-style UI.** Route to `summer:2d-assets/pixel-art` — different prompt pattern, different filter, different anchor.
+- **User wants pixel-style UI.** Route to `pixel-art` — different prompt pattern, different filter, different anchor.
 - **User wants animated UI (spinning loading icon).** Generate the static frame here. Animate via `AnimationPlayer` rotating the `TextureRect`, not as a sprite sheet.
 - **Transparency comes back as a checkerboard pattern in the image.** The model rendered the checkerboard literally because the prompt asked for transparency. Remove every mention of transparency from the prompt, generate on a plain background, and pass `options.removeBackground: true` to cut the alpha server-side.
 - **Icons need to read at very small size (16-24px in a packed bar).** Bias prompts toward bold silhouette + minimal interior detail. Ornate detail is invisible at 16px and adds noise.
@@ -212,13 +212,13 @@ After the UI graphic is wired:
 - **More icons in the same set** → re-invoke this skill with the same anchor.
 - **Button states (hover/pressed)** → re-invoke for each state.
 - **Theme assembly (combining icons + panels into a Summer Engine Theme
-  resource)** → `summer:scene-composition` for the resource wiring.
-- **Pixel-art UI** → `summer:2d-assets/pixel-art`.
-- **Dialogue UI with portraits** → `summer:2d-assets/character-portrait` for the portrait, then back here for the surrounding panel.
+  resource)** → `scene-composition` for the resource wiring.
+- **Pixel-art UI** → `pixel-art`.
+- **Dialogue UI with portraits** → `character-portrait` for the portrait, then back here for the surrounding panel.
 
 ## See also
 
-- `summer:2d-assets/character-portrait` — for in-UI character images.
-- `summer:2d-assets/pixel-art` — pixel-style UI.
-- `summer:scene-composition` — Theme and Control hierarchy.
-- `../../../references/mcp-tools-reference.md` — `summer_generate_image` schema.
+- `character-portrait` — for in-UI character images.
+- `pixel-art` — pixel-style UI.
+- `scene-composition` — Theme and Control hierarchy.
+- `../../references/mcp-tools-reference/mcp-tools-reference.md` — `summer_generate_image` schema.