scene-to-level

scene-to-level — From a reference image to a playable scene

This is the orchestrator skill. It does not generate art, slice sheets, or write game code. It routes the user through the chain of skills that do and stitches their outputs into a placeable Summer Engine scene.

Use it when the user shows you a screenshot or concept image and says "build this." The output is a .tscn you can hit play on, populated with assets that match the reference's style.

The pipeline (decision tree)

1. Read the reference image (vision).
   └── What kind of scene is it?
        ├─ 2D top-down / isometric / side-scroller
        │   └── route to TERRAIN + 2D ASSETS path
        ├─ 3D third-person / first-person
        │   └── route to 3D ASSETS path (out of scope for this skill —
        │       use summer:3d-assets/ subskills directly)
        └─ UI-only screen (menu, HUD)
            └── route to UI ASSETS path (just plan-asset-pack)

2. For each visible element, route to the right sub-pipeline:

   TERRAIN  → summer:2d-assets/tileable-texture
              (auto-tiling Wang / 47-tile sheet; CURRENTLY a placeholder
              that generates a single tile — full auto-tile work is
              tracked in publicsummerengine/Docs/assetCreation/
              TERRAIN_AUTOTILE_IDEA.md and not yet built)

   PROPS / DECOR / LIGHTING / NATURE / WATER / BUILDINGS / UI / VFX
       ── If user has time for individual generation, prefer:
       │   summer:2d-assets/create-asset-sheet (Plan + Generate Pack
       │   mode at /studio/plan-asset-pack — higher quality, each asset
       │   gets full model attention)
       └── If user wants fast / exploratory:
           summer:2d-assets/create-asset-sheet (Slice from a sheet at
           /studio/create-tileset — one sheet, autoslice, cheaper)

   CHARACTERS → summer:2d-assets/character-portrait first for the static
                frame, then summer:2d-assets/sprite-sheet for animation

3. Once assets exist, USE-WIDGET-ASSET on any UI / panel / bar /
   toggle pack files to wire them as NinePatchRect / TextureProgressBar
   / etc. (see summer:2d-assets/use-widget-asset)

4. Compose the scene:
   - summer_create_scene(path=..., rootName=..., allow_temporary_scene_mutation=true).
     It has no root-type argument: the new scene's root is copied from the
     currently-open (or main) scene's root, children stripped and root renamed.
     Start from a 2D scene if you want a Node2D root.
   - Add a TileMapLayer node for terrain; assign the generated tileset
     resource (`TileMap` is deprecated on the current Summer technical line)
   - Place props as Sprite2D / TextureRect children, positioned to
     match the reference's composition
   - Wire UI as Control nodes anchored to the viewport
   - Every mutation tool here takes a required `scenePath`

5. Validate:
   - summer_get_diagnostics (no args, project-wide) — or
     summer_get_script_errors(path="res://...gd") for one specific file
   - summer_play (the user takes over from here)