A filesystem-to-Studio sync workflow for Roblox projects. The goal is to safely understand the project structure, modify source code, and avoid breaking generated assets.
Workflow
- Identify the entry point:
- Look for
default.project.jsonor other*.project.json。 - Read the Rojo tree and confirm which directories map to
ReplicatedStorage、ServerScriptService、StarterPlayer、StarterGuiand other services. - Look for
wally.toml、aftman.toml、.luaurc、selene.toml、.stylua.toml。
- Look for
- Distinguish source files from generated artifacts:
- Prefer editing project source code outside
src/、Packages/. - Do not directly edit
.rbxl、.rbxm、.rbxlx、.rbxmx, unless the user explicitly requests it and explains the source. - Do not treat Rojo-generated sourcemaps as source code and hand-edit them.
- Prefer editing project source code outside
- Establish a path mapping before modifying code:
- Infer the Instance path in Studio from the project json.
- When modifying require paths, check both the callers and the dependencies.
- When adding a ModuleScript, confirm that it will be mapped by Rojo into the expected service.
- Run tools when available:
rojo sourcemapwally installstylua --checkselene- The project's built-in npm/pesde/lune/aftman scripts
- When delivering, explain:
- Which files will sync to which service in Studio.
- Whether the user needs to reconnect Rojo or Play Test in Studio.
Safety Boundaries
- Do not assume all Roblox projects use Rojo.
- Do not automatically rewrite the project structure.
- Do not delete package-manager-generated directories unless the user explicitly requests it.
- Do not treat manual object changes in Studio as already-synced facts; the user needs to provide an export or source mapping.
Output Format
- Rojo Mapping: project file paths to Studio service paths.
- Source Changes: specific files and module responsibilities.
- Needs Sync: actions that need to be performed on the Studio/Rojo side.
- Verification: list the Rojo/Wally/Luau tools that were run.