roblox-publish-checklist

사용 방법

설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.

npx skills add https://github.com/tabooharmony/roblox-brain --skill roblox-publish-checklist

시작 전 확인

설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.

원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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-data or roblox-server-data.
Remotes or authority changed: validate types, bounds, state, ownership, replay, and abusive frequency. Load roblox-networking and roblox-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.