unity-scene-create
Scene Bootstrap
Create scenes, add starter GameObjects, and attach initial components via unity-cli. This skill owns greenfield scene authoring; it hands off to unity-gameobject-edit or unity-prefab-workflow once objects already exist.
Use When
- The user wants to create a brand-new scene from scratch.
- The user asks to add initial GameObjects and components while bootstrapping a scene.
- The user needs help loading, saving, or organising a fresh scene authoring workflow.
Do Not Use When
- The request mainly mutates existing objects in an already-prepared scene; use
unity-gameobject-edit. - The work happens inside prefab edit mode; use
unity-prefab-workflow. - The user only wants to read or analyse a scene; use
unity-scene-inspect.
Preferred Flow
More from akiojin/unity-cli
unity-cli-usage
Bootstrap the unity-cli toolchain for Unity Editor automation. Use when verifying the unity-cli binary, choosing between typed subcommands and raw tool calls, switching active Unity instances, or troubleshooting host/port and install-mode issues. Do not use once a more specific Unity workflow skill applies; defer to `unity-scene-create`, `unity-csharp-edit`, `unity-editor-tools`, or another domain skill instead.
1unity-csharp-navigate
Explore Unity C# code without modifying files. Use when the user asks to read scripts, search text, find a symbol, trace references, inspect namespaces or packages, or understand where a class, method, or field is used. Do not use for code edits, renames, or refactors; use `unity-csharp-edit`. Do not use for scene inspection; use `unity-scene-inspect`.
1unity-development-loop
Run Unity runtime development loops with gameplay-focused implementation and validation. Use when the user asks to iterate on runtime behavior, reproduce and fix a gameplay bug, or implement a Unity-side flow until acceptance criteria are met. Do not use for `.inputactions` authoring, read-only inspection, or Rust CLI-only work.
1unity-playmode-testing
Drive Unity runtime verification with unity-cli. Use when the user asks to enter or exit play-mode, run an editmode or playmode test, simulate keyboard, mouse, gamepad, or touch input, capture a screenshot or video, or inspect current test status. Do not use for authoring input action assets; use `unity-input-system` instead.
1unity-scene-inspect
Inspect Unity scenes without mutating them. Use when the user asks to analyze scene hierarchy, list scenes, find a gameobject by name or component, inspect component values, review object references, or query animator state. Do not use for creating scenes; use `unity-scene-create`. Do not use for editing GameObjects; use `unity-gameobject-edit`.
1unity-input-system
Configure Unity Input System assets with unity-cli. Use when the user asks to create or remove an action map, add or remove an action or binding, set up a composite binding, inspect an input actions asset, or manage a control scheme. Do not use for runtime input simulation during tests; use `unity-playmode-testing`.
1