Repository navigation
docs: explain nested scene folders and scene creation decisions - #86
Merged
Merged
Conversation
JamieW105
added
area:website
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.
Explain how AI agents should organize scenes with meaningful nested folders and choose separate scenes for independent menus, loading screens and maps. Add a decision table, scene inventory example, exact authoring workflow, state-lifetime rules, loading limitations and end-to-end transition checks to the existing discoverable guides.
Validation: production build, ESLint with zero warnings, TypeScript, dependency audit (zero vulnerabilities), documentation structure/static-export checks, exported links/fragments and all four agent-documentation tests pass.
git diff --checkpasses.