Scene to level skill for AI agents

​

When your agent uses it

• Going from a scene reference image or concept art to a playable Summer Engine scene populated with the right assets and terrain
• The user shares concept art or a reference screenshot and wants that location built as a playable scene

​

Install

npx -y summer-engine@latest skills install scene-to-level --agent claude-code

​

The skill

​

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 `asset-strategy` directly)
        └─ UI-only screen (menu, HUD)
            └── route to UI ASSETS path (create-asset-sheet UI kit only)

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

   TERRAIN  → tileable-texture
              (auto-tiling Wang / 47-tile sheet; CURRENTLY a placeholder
              that generates a single tile — full auto-tile work is
              not yet built)

   PROPS / DECOR / LIGHTING / NATURE / WATER / BUILDINGS / UI / VFX
       ── Default: create-asset-sheet (one sheet, auto-sliced into a pack;
       │   fast and consistent in style)
       └── For a few hero assets that need full detail: generate them one
           at a time with pixel-art or character-portrait

   CHARACTERS → character-portrait first for the static
                frame, then 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 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)

​

When to use

• “Make this screenshot playable.”
• “I want a level that looks exactly like this concept art.”
• “Build a Japanese village scene like this reference.”
• “I have a UI mockup — implement it.”

​

When NOT to use

• The user wants a single asset → pixel-art or a leaf skill directly.
• The user wants to design a level from scratch (gameplay beats, pacing, encounters) → design-level. This skill is post-design — it implements a known visual target.
• The user wants a 3D level → use asset-strategy directly; the orchestration for 3D scenes isn’t in this skill yet.
• The user wants a playable prototype with mechanics already → mechanics aren’t in scope. This skill produces the visuals; the mechanic skills (e.g. design-mechanic) handle behavior.

​

Required up-front

1. A reference image (URL or local file) the user provides, OR
2. A vivid text description of the target scene from the user

​

Reliability map

​

A worked example

1. Vision pass identifies the scene as 2D isometric with: water terrain (large area), grass terrain (per island), buildings (5+ distinct), characters (2), UI palette + toolbar.
2. Props pack with create-asset-sheet: 12 props at minimum (torii, sakura, lantern, pagoda, bridge, well, sign, banner, bucket, hay, fence, crate).
3. Buildings pack: 5 distinct buildings (small house, barn, shop, pagoda, watchtower).
4. Terrain: today, a single grass tile, a single water tile and edge placeholders. Wang-tile auto-tiling is not built.
5. UI pack with create-asset-sheet and the theme “isometric voxel game UI: bottom palette, toolbar with Place/Erase/Pan/Save/Reset, asset category tabs, instruction panel.”
6. For each UI slice that is a panel or button, use use-widget-asset to wire it as a NinePatchRect.
7. Compose: TileMapLayer for terrain; Sprite2D placement matching the reference; Control nodes for the UI.
8. Validate and hand off.

​

What this skill explicitly defers

• 3D scene assembly. Out of scope; use asset-strategy directly until a 3D variant of this orchestrator exists.
• Auto-tiling terrain. The pipeline node exists in the decision tree but the leaf skill that implements it is not built.
• Animation orchestration. Per-character sprite-sheet is invoked manually; no auto-pairing of characters with their animation pipelines yet.
• Gameplay code. Player movement, interactions, win conditions — those are level-design + gameplay-mechanics skills, not this one.

​

From a shell

​

Related skills

• character-portrait: Generate one polished character bust for dialogue UI, character select, lore cards or codex entries.
• create-asset-sheet: Generate a pack of 2D assets from one prompt (tile sheet, UI kit, character pack, biome), sliced.
• pixel-art: Generate pixel-art sprites, items, tiles and portraits at a set resolution with a limited palette.
• sprite-sheet: Generate animated 2D character sprite sheets (walk, attack, idle, death) for AnimatedSprite2D.
• tileable-texture: Generate a seamless tileable texture for walls, floors or terrain, wired as a StandardMaterial3D albedo.
• use-widget-asset: Wire a widget slice from an asset pack (panel, button, bar, toggle) into NinePatchRect or TextureRect.
• design-mechanic: Design one mechanic in detail (input, feedback, failure modes, tunables) as a doc plus a script stub.
• design-level: Design one level (layout, pacing, encounters, secrets) as a design doc plus a node-tree skeleton.