Documentation
Write it, then look it up
Real pages for the product that exists: prompting, reasoning, Studio sync, accounts, and the HTTP surface. Nothing here describes a feature we faked.
Start
What Ripple is
A prompt-to-Luau studio that syncs a real Roblox project through our plugin.
Your first build
Sign in, describe a loop, wait for the agents, then pair Studio.
How to prompt
Write the fantasy, the loop, and one constraint. Skip lore dumps.
The workspace
Chat, explorer, and inspect sit on the same project. Nothing is decorative.
Ripple models
Flash, Core, Forge, and Ultra are product names routed in the database.
What Ripple is not
Honest limits so you do not expect a Roblox client in the browser.
Keyboard shortcuts
The few chords that actually do something.
Studio
Install the Studio plugin
A Luau plugin file. No master token is embedded.
Pairing codes
Short-lived codes exchange for a hashed, scoped token.
Pull and push
The website sends a revision. The plugin writes scripts. Studio can send edits back.
Studio errors
The plugin can report output errors. Iteration reads them.
Revisions
A revision is a snapshot after a successful generate or iterate.
Playtesting in Studio
Ripple ends at the revision. Studio is where you press Play.
Plugin HTTP surface
The four endpoints the plugin actually calls.
HttpService
Required for the plugin. Optional for generated games.
AI
The reasoning pass
Every build starts by thinking. You can read it in chat.
Agents
Reasoner, Architect, Asset Finder, Designer, Builder, Reviewer, Debugger.
Iterate in chat
Ask for a change. Ripple reasons, then edits only relevant files.
What Ripple will not pretend
No fake previews, no fake assets, no fake published games.
RemoteEvents and security
The builder should validate on the server. Review the output.
DataStores
Only generated when you ask, and only as Luau — not a hosted DB.
Library
Playbooks
Account
Accounts
Google, X, and email. Discord and GitHub are marked unavailable when they are.
Security
Scoped tokens, path normalization, rate limits, audit logs.
Publish and export
Publish puts a project on Discover. Export downloads JSON.
Members and sharing
Projects can have members in the database. Invites only exist if the UI exposes them.
Who can see what
Ownership, members, published slugs, and admin.
Billing
There is no checkout in this product yet.
Cookies and sessions
Auth cookies from Better Auth. No ad pixels.
Reference
Project structure
Services, remotes, and where scripts are allowed to live.
Luau conventions
What Builder is told to write.
Studio HTTP surface
Pair, status, pull, push, errors. All validated server-side.
Troubleshooting
The usual ways a build or sync stops, and what they actually mean.
Using the forum
Real threads from signed-in people. No seeded conversations.
Export
JSON of the project tree. Not an .rbxl.
How a project is stored
Instances, scripts, revisions, messages. Nothing decorative.
Rate limits
Builds, forum posts, and pairing are throttled on purpose.
Discover
Only published projects. The home cards are prompts, not games.
Forum moderation
Posts are real. Removal is admin-side.
Admin
Library ingest and model routes. Not a public console.