Como usar
- Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
- Consulte no original as ferramentas, credenciais e ambientes necessários.
- Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/tabooharmony/roblox-brain --skill roblox-publish-checklistAntes de começar
- A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
- Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.
Roblox Publish Checklist
When to Load
Load before publishing or updating a live experience. Test the surfaces and risks the change introduces.
Quick Reference
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. Load
roblox-dataorroblox-server-data. - Remotes or authority changed: validate types, bounds, state, ownership, replay, and abusive frequency. Load
roblox-networkingandroblox-security. - Purchases changed: test durable, idempotent receipt grants and retries. Load
roblox-monetization. - Cloud auth or webhooks changed: verify secrets, scopes, callback state, retries, signatures, and deduplication. Load
roblox-cloud.
A failed high-consequence gate means NOT READY. Do not average it into a percentage. Precedence: user approval authorizes an otherwise permitted action; it does not satisfy a mandatory policy and does not turn a failed or unverified gate into PASS.
3. Exercise the shipped surface
- Run one normal flow plus failure, retry, leave/rejoin, and rapid-input cases relevant to the change.
- Test every supported input mode and representative viewport/device tier.
- Measure errors, memory, frame/network cost and streaming.
- Verify focus, touch targets, readable contrast, non-color state cues, reduced motion, and localized overflow where applicable.
- Confirm Dashboard metadata, permissions and policy; after publishing, verify the version actually serving players.
4. Require evidence
Every PASS cites a test, log, profiler capture, readback, 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
