Repository navigation
docs: teach agents scene organization and scene boundaries - #85
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agents currently have scene tools but little guidance on when to split screens/maps or how to keep a growing hierarchy organized. Expand the bundled authoring and scene-explorer skills with nested-folder examples, a scene decision table, menu/loading/Map1/Map2 workflows, state ownership, path conventions and transition verification.
Route agents to that guidance from MCP initialization, generated project instructions and the existing scene/object tool descriptions. Preserve customized integration files and the existing guide-tool upgrade path. Update the engine-local documentation to match.
Validation:
git diff --checkpasses; manually checked tool contracts, folder transforms, persistence and scene lifecycle against implementation. Confirmed new guide sections match the corresponding documentation text.Blocked validation: Cargo/Rust is not installed, so engine tests could not run. The required Windows installer command also fails because PowerShell is unavailable; no fresh installer was produced. This PR remains a draft pending those checks.