spatial-placement

Place and verify 3D objects in scenes using Starcast collision evidence.

66|4|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/SummerEngine/summer --skill spatial-placement-summerengine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spatial-placement
Source: https://github.com/SummerEngine/summer/tree/main/library/skills/spatial-placement
Command: npx skills add https://github.com/SummerEngine/summer --skill spatial-placement-summerengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Placing 3D objects in a game scene often results in floating props, overlapping colliders, or blocked clearances that are hard to detect without evidence. This Skill provides a disciplined inspect-place-verify loop so every placement is grounded in actual physics and bounds data rather than guesswork. ## Core Features & Use Cases - Evidence-driven placement loop: Inspect the scene tree, place the object, query Starcast for support and clearance evidence, correct only the axes the evidence flags, and verify the result. - Placement recipes: Ready-made criteria for floor, shelf, wall, alcove, and rotated-object placements, plus an overlap-repair procedure that moves along the clearest axis. - Result interpretation guidance: Explains grounded status, contact detection, directional clearance, and the difference between exact physics evidence and approximate visual AABB evidence. - Use Case: You need to set a lamp on a shelf without it clipping the back wall. The Skill inspects the scene, places the lamp, runs a Starcast summary, corrects the blocked axis, and confirms support and forward clearance. ## Quick Start Ask the agent to place the crate on the shelf in the current scene and verify with Starcast that it is supported and not overlapping anything.

Frequently Asked Questions about spatial-placement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I place a 3D object on a shelf without overlap in Summer Engine?

Inspect the scene tree to get exact node paths, place the object approximately with summer_set_prop or summer_batch, then run summer_starcast with detail="summary". Correct only the axes the evidence flags and re-verify until support and clearances are satisfied.

How do I fix a floating or overlapping object after placement?

Run a Starcast summary to identify contacts and blocked directions, then move the object along the clearest axis with the shortest correction and rerun the check. Do not resize the asset unless the user explicitly requested it.

Does Starcast placement work in 2D scenes?

No. Starcast reads Node3D bounds, 3D physics, and visual AABBs, so this Skill does not apply to 2D scenes. It also requires Summer Engine 0.5.66 or newer, since earlier builds return engine_lacks_op.

What is the difference between physics and visual_aabb evidence in Starcast?

Physics evidence is exact collider-query data, while visual_aabb includes visible meshes without colliders but is a world-axis-aligned broad-phase approximation. You should not infer exact surface contact from visual_aabb results.

When should I use local versus world directions for placement checks?

Use local directions only when placement is defined relative to a rotated subject, such as its own front or side. Use world directions for level axes like floors, walls, and general clearances.