roblox-publish-checklist
Skill2 starsChanged 31 days agoMITView on GitHub
Evidence-backed release gate for a Roblox experience: classify gates, block on persistence, remote, purchase and cloud failures, exercise the shipped surface, check Creator Dashboard settings, and report READY / NOT READY / READY WITH ACCEPTED RISK. Use before publishing or updating an experience, restarting servers, or when asked whether a build is ready, safe or tested enough to ship.
3 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- ForgeyClap/Forge-Coreedited, first seen Nov 16, 2026
- TabooHarmony/roblox-brainedited, first seen Sep 23, 2026
- szlay/roblox-basetheir own version, first seen Jul 24, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- TabooHarmony/roblox-brain★ 15039% same
- ForgeyClap/Forge-Core★ 236% same
Wrote their own version · 1
- szlay/roblox-base★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- template/CLAUDE.mdCLAUDE.md
- roblox-lessonsSkill
- audio-designSkill
- game-feelSkill
- game-ui-uxSkill
- level-designSkill
- roblox-creator-store-security-auditSkill
- roblox-dataSkill
- roblox-debugging-bugfixSkill
- roblox-devSkill
- roblox-monetizationSkill
- roblox-networkingSkill
- roblox-release-operationsSkill
- roblox-security-economySkill
- roblox-securitySkill
- roblox-studio-mcpSkill
- roblox-to-issuesSkill
- roblox-toolingSkill
- save-systemsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 2 are common, 1 is distinctive, and 0 are very specific to this project.
2
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 26
Every supported input mode and representative viewport/device tier.
- Distinctive: line 35
Every pass/product id and display price matches the dashboard.
- Common: line 42
Every PASS cites a test, log, MCP readback, profiler capture, screenshot or dashboard inspection.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Roblox publish checklist
Where this conflicts with the roblox-lessons skill, roblox-lessons wins.
1. Define the release
Record the changed places, scripts, assets, configuration, schemas, products, supported devices and rollback path. Classify each gate as required, conditional or not applicable before testing.
2. Block on high-consequence failures
- Persistence changed: load, save, migration, duplicate-session, disconnect and shutdown behavior (
roblox-data). - Remotes or authority changed: types, bounds, state, ownership, replay and abusive frequency (
roblox-networking,roblox-security). - Purchases changed: durable, idempotent receipt grants and retries; paid-random-item restrictions honoured (
roblox-monetization). - Cloud auth or webhooks changed: secrets, scopes, retries, signatures, deduplication (
roblox-lessonsreferences/open-cloud.md).
A failed high-consequence gate means NOT READY; never average it into a percentage. User approval authorizes an otherwise permitted action; it does not satisfy a mandatory policy or turn a failed or unverified gate into PASS.
3. Exercise the shipped surface
- One normal flow plus failure, retry, leave/rejoin and rapid-input cases relevant to the change.
- Every supported input mode and representative viewport/device tier.
- Errors, memory, frame/network cost and streaming.
- Focus, touch targets, contrast, non-color state cues, reduced motion, localized overflow where applicable.
- Dashboard metadata, permissions and policy; after publishing, the version actually serving players.
4. Hub gates (from roblox-lessons)
- Studio-only conveniences (starting grants, force-owned passes, test runners) are guarded by
RunService:IsStudio(). - Studio saves go to the
_Studiostore; production store names unchanged (no rename to change a format). - Every pass/product id and display price matches the dashboard; prices are 2 R$ or more.
- Paid random items: odds shown before purchase; restricted players blocked from currency products, roll shortcuts and odds-changing passes; questionnaire answered "yes" to paid random items.
- Publishing ships from Studio: Rojo sync finished and the place saved before publishing (place-file art lives only there).
- The human owner decides prices, visibility and publishing; an API key cannot make a game public or upload thumbnails.
5. Require evidence
Every PASS cites a test, log, MCP readback, profiler capture, screenshot or dashboard inspection. UNVERIFIED if unavailable; approval is not evidence.
Output
READY, NOT READY, or READY WITH ACCEPTED RISK; blockers first, then warnings, unverified gates, evidence, rollback plan, and skipped gates with reasons.
Details: references/full.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

