wayzoo/wayzoo-skill

Write Roblox in TypeScript. Compile to Luau. Burn far fewer AI tokens.
Wayzoo is a Claude skill plus a few small Node scripts. Claude writes the TypeScript once, roblox-ts compiles it, and the Luau reaches Roblox Studio without the AI ever reading or retyping it. It runs natively on Windows (no WSL, no Bash), macOS and Linux.
Install in 1 minute (Claude web or desktop app, any OS): download dist/wayzoo.skill, then in Claude open Customize > Skills, click +, choose Create skill > Upload a skill, pick the file and switch the skill on. Then ask Claude to write your Roblox code in TypeScript. More options in INSTALL.md.
## Contents
The problem · How Wayzoo helps · Measured savings · Install · Commands · Roblox Studio and MCP · Repo layout · FAQ · Contributing
## The problem
A naive AI + roblox-ts loop pays for the same code three times:
1. the AI writes the TypeScript,
2. it reads the compiled Luau back to check it,
3. it pastes that Luau into Studio.
Failed builds also dump a wall of compiler output into the chat. And the AI often guesses which @rbxts packages exist and invents import paths. On a big game this adds up fast.
## How Wayzoo helps
| Trick | Effect |
| build prints one line on success, only the first N lines on failure | Failed builds don't flood the context |
| Import errors (TS2307...) come first, with the faulty and expected path | Fewer hallucinated import paths |
| deps lists installed @rbxts packages in a few lines | The AI uses real packages, never reads node_modules |
| Compiled .luau is never printed or re-read | It is a build artifact, not something to review |
| Only changed files are reported and sent | No re-sending the whole project |
| Rojo live sync | Code reaches Studio without passing through the chat |
| Studio MCP used for live state only | Errors, instances, playtests, not source code |
More detail in docs/how-it-works.md.
## Measured savings
Run on a generated 12-function TypeScript file (about 3.3 KB, compiling to about 3.6 KB of Luau). Sizes are bytes of text; tokens scale roughly with that.
### Context used per build cycle (lower is better)
text
Naive AI loop [████████████████████████████████████████] 10.6 KB baseline
Wayzoo + Roblox Studio MCP [██████████████████████████ ] 7.0 KB -34%
Wayzoo + Rojo sync [█████████████ ] 3.4 KB -68%
The naive loop pays for the compiled Luau twice (read back, then pasted into Studio). With the Studio MCP, Wayzoo pushes each changed Luau file once and uses the MCP only for live telemetry. With Rojo, the Luau never enters the conversation at all: the AI gets one status line and Rojo syncs the rest.
### Benchmarks
| Scenario | Naive loop | Wayzoo strategy | Saving |
| Code to Roblox Studio via Rojo | ~10.6 KB | ~3.4 KB (silent local compile, Rojo sync) | about 68% |
| Code to Roblox Studio via MCP, no Rojo | ~10.6 KB | ~7.0 KB (changed Luau pushed once, MCP for telemetry only) | about 34% |
| TS compiler output with 25 type errors | ~3.4 KB | ~1.2 KB (truncated, import errors first) | about 65% |
Best setup for Roblox Studio: Rojo for code + Studio MCP for Output and playtests. That keeps the 68% saving on code and adds live debugging without paying for source again.