$npx -y skills add TabooHarmony/roblox-brain --skill roblox-architectureUse when starting or refactoring a Roblox project, choosing service or module structure, or making client-server architecture decisions.
| 1 | # roblox architecture |
| 2 | |
| 3 | ## When to Load |
| 4 | |
| 5 | Load when deciding where code and assets belong, introducing service or controller modules, or changing the client/server boundary. |
| 6 | |
| 7 | ## Quick Reference |
| 8 | |
| 9 | - Put authoritative game rules in `ServerScriptService`; keep server-only templates and secrets in `ServerStorage`. |
| 10 | - Put only genuinely shared modules, remotes, and public assets in `ReplicatedStorage`. |
| 11 | - Treat `LocalScript` code and replicated contents as observable and modifiable by the player. |
| 12 | - Give each module one owner and one clear contract. Use signals or a coordinator for cross-system communication instead of circular `require` calls. |
| 13 | - Use one small bootstrap on each side, then initialize feature modules in an explicit order. |
| 14 | - Keep UI and input controllers on the client. Keep rewards, inventory, combat outcomes, and persistence on the server. |
| 15 | |
| 16 | **Need the details?** Load `references/full.md` for layouts, lifecycle code, and boundary checks. |