Roblox Rojo (Filesystem Workflow)

How to develop Roblox games with files on disk instead of inside Studio. Sources: rojo.space (official Rojo docs), github.com/rojo-rbx/rojo (Rojo source), github.com/rojo-rbx/rokit (Rokit toolchain manager — use this, not Aftman/Foreman), github.com/UpliftGames/wally (Wally package manager), github.com/pesde-pkg/pesde (Pesde — newer alternative package manager). Tooling: stylua, selene, luau-lsp.

For deep dives see:

• references/project-format.md — full .project.json schema
• references/sync-mapping.md — every file extension Rojo recognizes and what it becomes
• references/wally-manifest.md — full wally.toml + lockfile + command reference
• references/pesde-manifest.md — full pesde.toml schema, environments, Wally bridge
• references/luau-lsp-setup.md — sourcemap regen, LSP configuration

Integration Policy

This skill describes preferred patterns; it does not authorize rewriting existing code. Apply rules to new code and to changes the user explicitly asks for. Match the codebase's existing toolchain. If the project uses Aftman, don't migrate to Rokit unprompted. If it uses Wally, don't suggest Pesde. If default.project.json follows a particular structure, extend it — don't rewrite it. Surface conflicts once and default to the existing setup.

Full rules: ../../shared/integration-policy.md.