> For the complete documentation index, see [llms.txt](https://docs.roomle.com/rubens/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roomle.com/rubens/content-creation/scripting-course-and-resources/200_10_prerequisities.md). # Prerequisities for Roomle Content Scripters This document sums up recommended skills and prerequisities for scripting Roomle content (= writing component definitions). Note, that a lack in some of these skills does not mean you can't be a good scripter! ### Programming skills * ability to design and implement algorithms * a feeling for object oriented programming (components act as objects, including inter-component data interactions) * knowledge of any specific API not required * basic programming consturctions (variables, expressions, conditions, loops, arrays) * code versioning, preferably using Git * ability to write understandable and maintainable high quality code, that follows good practices ### 3D graphics basics This theoretical knowledge is not essential for scripting Roomle content, but are highly recommended and advantageous to study eventually: * RGB color space * textures * normal maps * shader values: roughness, metallicity, alpha, etc. * primitives, meshes, sketches, extrusion * vertices, triangles, normals, UVs * transformations: movement, rotation ### Other non-mandatory, but advantegeous skills * communicative knowledge of English (we have most documents and task descriptions in English, we also communicate in English or German) * comments and ids should be unviversally written in English * it is an advantage to understand products' origin language (to understand manufacturer's drawings, catalogues etc.) * the most common language of produced configurator outside of English is German * 3D vector algebra * position and normal vectors * transformations * coordinate systems * CAD, construction, engineering * to understand and be able to measure in drawings, CAD models etc. * 3D game engines * experience in 3D game development - Unity3D, Unreal etc. * because there you also bring 3D graphics to live :) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.roomle.com/rubens/content-creation/scripting-course-and-resources/200_10_prerequisities.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.