Architect for Roblox

Design before implementation. This is a design gate, not a reason to expand scope. Read ../../references/roblox-engineering.md first. Repository instructions and the current source outrank this skill. Use the contract's Repository mode or Studio fallback mode; never use Roblox Studio MCP playtest controls.

Before delegating or using optional capabilities, read the runtime contract. It owns eligibility, model selection, limits, and fallback.

The selected high-capability parent owns the design, dependency order, and difficult implementation. Delegate source inventories, bounded evidence gathering, routine modules under settled interfaces, and fixtures through the runtime worker policy. Inspect worker artifacts and resolve their questions before accepting a design or implementation unit.

Choose the depth

Classify the change before doing deep work:

• Local: one clear owner, one module, no public/shared API, remote, server-owned state, persistence, replication, lifecycle, or authored-asset boundary. Produce a compact sketch. Skip $arena, $how, and $why unless evidence is missing.
• Integrated: crosses two or more modules or services, or changes a public/shared API, remote contract, server-owned state, persistence, replication, lifecycle ownership, or authored assets. Run Ground and Sketch before implementation.
• Load-bearing: adds a migration, monetization or purchase path, consequential RNG, security boundary, physics/network ownership, broad refactor, or an irreversible contract. Use Integrated depth, compare whole-shape alternatives, and consider $arena or $interrogate only when the ambiguity or risk justifies the cost.

Start

Keep a compact phase checklist so work does not silently skip a design step: