Documentation
How RoBuild works
This page covers the core concepts. It will grow into full product documentation as RoBuild launches — nothing here describes a feature that isn't actually built yet.
The generation pipeline
1. Describe
Tell RoBuild what you want in plain English.
2. Understand
RoBuild reads your project's real Explorer hierarchy and scripts.
3. Review
Every proposed change is a diff you accept or reject.
4. Ship
Accepted changes land in your project, ready to publish.
Luau conventions RoBuild follows
Every generation is guided by a fixed set of rules, not freeform improvisation:
- Generates Luau, not generic Lua
- Respects client/server boundaries — never trusts client RemoteEvent input without validation
- Wraps risky calls (DataStore access, HTTP requests) in pcall
- Avoids deprecated Roblox APIs
- Prefers modular architecture (ModuleScripts over duplicated logic)
- States required Instances and file placement explicitly
- Flags uncertain assumptions instead of guessing silently
Default project structure
New projects start with the standard Roblox service categories, ready for RoBuild or you to organize:
WorkspaceReplicatedStorageServerScriptServiceServerStorageStarterGuiStarterPackStarterPlayerSoundServiceLighting