> For the complete documentation index, see [llms.txt](https://imagineee.gitbook.io/orbs-js/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://imagineee.gitbook.io/orbs-js/docs/structure.md). # Structure The structure of orbs js is simple with each sprite, image, scene, renderer, script, vector being an object or also known as object oriented. There are multiple objects at your disposal each having small and large functions that can save you time during development. Another main feature of orbs js is its values system which allows you to choose values, reuse values, not type inverted commas and no misspelling. An example might be you need to define `'down'` in your code for mouse button down and your collision detection also needs it, instead of writing the word `'down'` all you need is to use the variable down, this also can be used to e consistent with the engine and cause less errors, but now a days this method adds a lot of dead weight to the code base and might be discontinued in the future. ### Your Project Structure Your project structure should be simple with importing values and functions in the top, setting up render and scene next and adding any images before rendering, a cool feature in orbs is the css to make your project full screen with [this (sorry for no docs on this coming later)](https://github.com/imagineeeinc/orbs-js/blob/main/src/orbs.js#L933), then creating and defining objects and adding to scene, lastly attaching scene to renderer and staring render cycle. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://imagineee.gitbook.io/orbs-js/docs/structure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.