ashexplained/roblox-skills

roblox-to-prd

Turn a Roblox game concept or the current conversation into a short, buildable PRD (game design brief) and publish it to the project tracker.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/ashexplained/roblox-skills --skill roblox-to-prd

시작 전 확인

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

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

Roblox → PRD

Turn what is already decided into a concise, buildable game design brief (PRD). Do NOT interview the user from scratch — synthesize the concept, conversation, and place state you already have. If the concept has not been pressure-tested yet, run roblox-game-ideas (grilling mode) first.

The tracker location and label vocabulary should have been provided to you in CLAUDE.md / docs/agents/. If not, run setup-roblox-skills.

Why this exists

The single biggest failure mode in AI-built Roblox games is trying to build the whole game in one pass, which leaves everything half-working. A PRD is the contract that a later step (roblox-to-issues) slices into small, independently playtestable pieces. Keep it tight: enough to slice, not a novel.

Process

  1. Read the current state. Connect through roblox-studio-workflow if a place exists. Read ROADMAP.md if present. Use the game's own vocabulary consistently (currency names, entity names, zone names).
  1. Sketch the systems, not the whole game. List the major server-authoritative systems and client controllers this concept needs (core loop, economy, save/load, progression, social, UI surfaces). Flag which hold valuable state (currency, inventory, purchases, rewards, progression) — those must be server-authoritative. Confirm the system list matches the user's expectation before writing.
  1. Handle UI up front. If the concept has meaningful UI, note whether a Roblox UI design artifact exists yet (see roblox-game-ux). If not, record an explicit design step rather than treating UI as ready to build.
  1. Write the PRD using the template, then publish it to the tracker with the needs-triage label/status so it enters the normal flow.

<prd-template>

Player Promise

What the player gets, in their words. One or two sentences.

Core Loop

The single repeating loop, start to reward to next goal. Name the first fun action and how fast it happens (target: 10–30 seconds).

First Session

What the first 30–60 seconds look like: spawn, first action, first reward, first visible goal.

Systems To Build

A list of the server-authoritative systems and client controllers. For each: one line on what it does and whether it holds valuable state (server-authoritative) or is client-side presentation.

Player Stories

A numbered list, format: "As a player, I want <capability>, so that <benefit>." Cover the core loop, progression, social, monetization, and mobile paths. Extensive but plain.

Economy & Monetization

Currency sources and sinks, what is sold (passes, developer products, cosmetics), and the anti-pay-to-win rule for this game. Write "None yet" if pre-monetization.

Persistence

What must survive rejoin/shutdown (currency, inventory, progression, settings) and what is session-only.

UI & Design

Which surfaces need a UI design artifact (HUD, shop, reward, menus) and whether that artifact exists and is approved. For non-UI PRDs, write "No UI design step required."

Mobile & Performance Targets

Mobile-first expectations (touch targets, readability, safe areas) and any frame-rate/instance budgets.

Out Of Scope

What this PRD deliberately does not cover, so slicing stays focused.

Risks

The top 1–3 risks and how each is checked (usually a Studio playtest).

</prd-template>

Next

Hand the published PRD to `roblox-to-issues` to break it into small, playtestable vertical slices. If the PRD flagged UI work, run `roblox-game-ux` to produce and approve the UI design artifact before UI slices become buildable.

같은 저장소의 Skills

더 많은 Skills

모든 Skills
ashexplained
커뮤니티

roblox-playtest-qa

Playtest Roblox experiences through Studio MCP with attention to first-session fun, mobile UX, console errors, progression, social hooks, performance, and exploit-sensitive flows.

1시간 설치 수
4
GitHub Stars
63
업데이트
7월 1일
ashexplained
커뮤니티

roblox-animation-audio-feedback

Improve Roblox feel through animation, audio, VFX, haptics-like feedback, reward juice, movement feel, combat feedback, UI transitions, emotes, and satisfying loop feedback without hurting mobile performance.

1시간 설치 수
3
GitHub Stars
63
업데이트
7월 1일
ashexplained
커뮤니티

roblox-combat-systems

Design, implement, and review Roblox combat systems. Use for melee, ranged, abilities, cooldowns, hit detection, damage validation, status effects, enemy AI hooks, combat UI, balance knobs, VFX/SFX, and exploit-resistant remotes.

1시간 설치 수
3
GitHub Stars
63
업데이트
7월 1일
ashexplained
커뮤니티

roblox-creator-store-security-audit

Audit Roblox Creator Store, Toolbox, inventory, group, universe, package, model, UI, gameplay, plugin-like, and other third-party imported assets for malicious or risky scripts. Use whenever Claude imports, inserts, reviews, or trusts Creator Store assets, especially assets with Scripts, LocalScripts, ModuleScripts, hidden descendants, require calls, HTTP, DataStore, remote creation, obfuscated code, or suspicious names.

1시간 설치 수
3
GitHub Stars
63
업데이트
7월 1일