What your agents can do

Seventeen Roblox skills, added to each project when it opens.

A generic AI agent knows Roblox only in general terms. Yours knows your project template, because VibeStarter adds instructions and skills written for it to each project. That is the difference between “an AI that codes Roblox” and an agent that knows where every file of your game goes.

What VibeStarter adds to your project

When you open a project, the app writes the following to it:

an instruction file for each agent family, with the shared rules and the description of your project template;
seventeen skills — step-by-step guides for specific tasks that the agent reads before it works.

These files are excluded from your game’s history: they don’t clutter your versions. You don’t have to install anything, turn anything on, or type anything.

The seventeen skills

Designing your game

Skill	What it does	A request that triggers it
`roblox-brainstorm`	Runs a brainstorming session in four stages: framing questions, a brief you correct, three truly different concepts, then the game loop. It converges with you instead of dumping a list.	“I want to make a Roblox game but I don’t know what — help me find an idea.”
`roblox-game-design`	Gives a designer’s view of your game loop, your opening, your retention and your pacing. It marks each claim as observed, reported or inferred, and gives three recommendations, not ten.	“Players leave after two minutes, why?”
`roblox-game-balance`	Tunes the numbers: currency gains, experience curve, damage, drop rates, prices, rebirth costs. It reads your real data files and maps every source and every spending of currency.	“The start is too long and the end is too easy — audit my progression.”
`roblox-monetization`	Designs Game Passes, Developer Products, shops and packs, with prices in Robux. It reads your code to find the real friction points.	“Design a shop and a starter pack for me, with prices.”

Building the game

Skill	What it does	A request that triggers it
`roblox-backend`	The game engine: combat, economy, matchmaking, saving player data, server and client sync. Two golden rules: the server is in charge, and each player is only sent what they need.	“Add coins earned by beating mobs, saved between sessions.”
`roblox-ui`	All the interfaces: menus, HUD, shops, inventories, popups, leaderboards. It applies the scaling that makes an interface fit every screen, not only 1080p.	“Add a health, coins and level HUD that also works on mobile.”
`roblox-mapping`	Builds the world: biomes, architecture, interiors, decoration, placement, ground anchoring, lighting. It builds in layers, with a check between each, and casts rays when anchoring matters.	“Build a forest with a path climbing to a ruined temple.”
`roblox-multiplace`	Games with several worlds: teleporting between places, several Studio windows, publishing a multi-place experience.	“My game has a lobby and a battle map — add teleporting.”

Visuals and motion

Skill	What it does	A request that triggers it
`roblox-icon`	Makes the game’s 2D images: item, skill, currency and badge icons, portraits. It asks the server for the canonical prompt instead of writing its own, so two icons made a month apart look alike.	“Make the icons for my six spells, all in the same style.”
`roblox-asset-reuse`	When you point to an asset already in your game, it fetches the real file and edits it instead of generating a lookalike. For a series, it validates a base and then derives each variant from that base.	“Take the chest icon already in the game and make a gold version.”
`roblox-model-parts`	Decides whether a model should be split so it can move in pieces — and asks you before spending, because each part becomes a MeshPart with its own textures.	“My chest is a single block, I want the lid to open.”
`roblox-motion`	Animates characters: attacks, combos, walking, running, jumping, dodging, hit reactions, emotes, bosses, mounts. It writes the motion as code evaluated every frame, so the stride adapts to speed instead of sliding.	“Animate my boss: a heavy sword attack, an idle, a walk.”
`roblox-object-motion`	Everything that moves but isn’t a character: machines, vehicles, turrets, doors, gears, plus the ambient life of a scene.	“My map feels dead: grass that sways, a windmill that turns.”
`roblox-vfx`	Visual effects: impacts, explosions, spells, fire, smoke, auras, portals, screen shake. Its core lesson: more particles, bigger and brighter, make a hit feel weaker, not stronger.	“My sword attack doesn’t feel like anything — add a real impact.”
`roblox-vfx-sprite`	Draws a custom particle texture — slash crescent, rune, cracked ground decal, snowflake — in code, without a starting image.	“I want a real crescent shape for my slash.”

Publishing and working with others

Skill	What it does	A request that triggers it
`roblox-release`	Publishes a version. The agent doesn’t improvise: it checks that the project compiles, saves, and sends you to the right button. Rolling back is a roll forward: nothing is lost.	“What has changed since the last live version?”
`merge-resolver`	The safety net for teamwork. In the rare case where two people changed exactly the same lines, a dedicated agent is started automatically, merges while keeping both sides, and proves that it compiles. If it can’t do that cleanly, it stops without saving anything.	Triggered by the app.

The rules your agents always follow

Your language. The agent reasons and codes in English, but answers you in the language chosen in VibeStarter, including when it picks up a conversation started in English. Code identifiers stay in English. An explicit request from you for another language takes priority.
It reads the guide before it writes. Any interface goes through roblox-ui, any server work through roblox-backend, any animation through roblox-motion, any map construction through roblox-mapping.
It remembers. Tell it “remember that…” and it writes a note in the user-notes/ folder of your project. You find it in the notes panel, on the left, where you can read, edit or delete it.
It writes your documents in the right place. Design document, concept, guide, report: everything goes into user-notes/, because the notes panel only lists that folder. A document written elsewhere would be invisible in the app.
It doesn’t compile by itself. A managed process already compiles continuously. It only checks the result.
It can tell a bug from a lack of memory. When compilation fails for lack of memory, it explains that closing agents frees memory and stops, instead of changing code at random.
It never asks you to paste a Roblox key into the conversation. For monetization, it opens and highlights the field provided in the settings. See Link your Roblox account and your Open Cloud key.
It doesn’t destroy an existing map without asking you. Your maps are treated as read-only by default: even for a request that sounds like a rebuild, it stops and asks for explicit confirmation, or it builds next to it.
It puts the Studio camera back after moving it.
It waits its turn on a place. Only one agent drives a place at a time.

What your agents cannot change

Three files in your project are locked at the file system level: default.project.json, tsconfig.json and scripts/dev.mjs. Any attempt to change them fails. The instructions that were added say so to the agent in plain words, so it doesn’t keep trying. If you see an agent stuck on one of them, this isn’t a bug: the protection is doing its job.

How these skills get updated

The skills are refreshed every time a project opens: a fix published on our side reaches you without updating the app. Only the ones that rely on a newer app feature wait for the app to be updated. See Update the app.

Two behaviors to know about:

First opening of a project without a network connection: opening is blocked, with an explicit message. This is intentional — it’s better to refuse than to have an agent work without its instructions.
Project already opened once: if the content update fails, the files already on your disk are kept and you keep working.

Limits

Your agents don’t check your game’s statistics. This isn’t implemented yet.
An agent sometimes gets its own abilities wrong and claims that a feature doesn’t exist. Give it the instruction again explicitly, or clear the context with /clear and start it again.
Editing the instruction files yourself is pointless: they are rewritten at every update. For a lasting instruction, tell the agent “remember that…”: it writes it in user-notes/ and rereads it when a request depends on it.
Monetization is reserved for the project owner. An invited collaborator simply doesn’t get these tools.

Frequently asked questions

“What can I ask it?” Look at the right-hand column of the tables above: these are real requests, written in French, that are enough to trigger the right skill.

“Do I have to type a command to activate a skill?” No. The agent picks the one that matches your request on its own.

“Is my code saved during all of this?” Yes, automatically. The agent doesn’t manage branches or a remote repository: it saves your work as it goes. See Your code is saved automatically.

“My agent tells me VibeStarter can’t do X.” That’s a known mistake on its part. Check this documentation, then insist: “use the skill intended for that”.

Going further

VibeStarterBack to the websiteDocumentation for version 3.6.3 of the app