You type a request in the chat panel inside Roblox Studio. Can be simple: "Add a leaderboard sorted by Coins." Or complex: "Refactor the entire shop system to support multiple currency types." Plain English always works. Lua pseudocode works too.
Before writing a single line, I list your existing files and read the relevant ones. I want to understand what's already there, what naming conventions you're using, and what I might accidentally break if I'm not careful. I'm thorough about this.
I tell you what I intend to create or modify, and why. If I think there's a better approach than what you described, I'll say so — clearly and without being condescending about it. You can redirect me before I touch anything.
I write Lua that fits your workspace style. That means using your existing patterns, your naming conventions, your DataStore setup — not a generic template. Multi-file tasks are coordinated: I don't write a server script that references a RemoteEvent that doesn't exist.
Every proposed change is shown as a diff — additions in green, removals in red, context lines in grey. You read it. You can approve all, reject individual hunks, or ask me to revise. Nothing changes in your workspace until you say OK.
After approval, I summarise what changed: which files were created or modified, what the changes accomplish, and anything you should know or test. The full session is saved to History so you can review it at any time.
Knowing my limits is just as important as knowing my capabilities. I'd rather be honest than overpromise.
The team that built me is from Maple Grove, Minnesota. And there's a real culture there — one that values directness without rudeness, helpfulness without condescension, and honesty without drama. That's what I'm designed around.
You'll notice it in how I talk to you. I won't hype you up with hollow praise when something doesn't work. I won't be cryptic about what went wrong. I'll just tell you clearly, calmly, and with enough context to actually understand it.
I treat your code with respect. Even if I think a different architecture would serve you better, I'll say "I'd suggest…" not "this is wrong."
Not getting what you want from me? That's on me to explain better, or on me to ask better questions. I don't get frustrated.
I'll tell you what tools I called, what they returned, and why I made the decisions I did. No black boxes.
Your instincts about your own game are valuable. I bring knowledge; you bring context. The best results come from both.
ScriptWEAVER is designed so that the developer always has the final say. Here's every lever you control.
Every proposed change surfaces as a line-by-line diff. Approve all, approve selectively, or reject entirely — your call, every time.
Every Wren job is stored in the History panel. See what was changed, when, and which model ran it. Use it for auditing or learning from past sessions.
Pick Speed, Balanced, or Quality for each job. You control the speed-vs-depth tradeoff based on what the task actually requires.
If Wren is heading in the wrong direction, stop the job at any point. No partial writes are applied without your explicit approval of the diff.
Not happy with the result? Ask me to revise with feedback, or start a new session with adjusted instructions. Sessions are independent.
Approved something you regret? The session history shows exactly what was changed. Use Roblox Studio's built-in version control or git to revert. We'll add integrated rollback in a future version.
I'd rather answer these directly than have you find out the hard way.