gdd

스타8

포크0

업데이트2026년 4월 15일 20:51

Create or update a Game Design Document. Use for master GDD creation, system-specific GDDs, or GDD review. Invoke with /gdd [system-name] for a specific system, or /gdd for the master document.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

CodePhobiia

CodePhobiia/claude-roblox-game-studio

GitHub 저장소 열기 Creator 저장소 보기

다운로드

/gdd — Game Design Document Workflow

If no argument provided (Master GDD):

Create the master GDD at design/gdd/master-gdd.md using the template at .claude/docs/templates/gdd-master.md.

The master GDD must include:

Game Overview: Concept, genre, platform (Roblox), target audience
Creative Pillars: 3-5 pillars that guide all decisions
Core Loop: 30-second, 5-minute, session, and meta loops
Systems Overview: List all game systems with 1-sentence descriptions
Player Progression: How do players grow over time?
Monetization Strategy: GamePasses, DevProducts, Premium Benefits
Social Features: Multiplayer, trading, guilds, parties
Target Metrics: D1/D7/D30 retention targets, session length goals
Content Plan: Launch content vs. future updates
Technical Overview: Client-server split, DataStore approach, key technical constraints

If argument provided (System GDD):

Create a system-specific GDD at design/gdd/<system-name>-gdd.md using the template at .claude/docs/templates/gdd-system.md.

Every system GDD must include:

Overview & Purpose
Core Mechanics (detailed)
Data Schema (DataStore keys, types, defaults)
Client-Server Split (what runs where)
RemoteEvents/Functions needed (with argument contracts)
Player-Facing UI (mockup or description)
Edge Cases & Error States
Balancing Parameters (formulas, not magic numbers)
Integration Points (dependencies on other systems)

Workflow Steps

Ask Context: "Are you creating a new GDD or updating an existing one?"
Delegate: Route to game-designer agent for master GDD, or systems-designer for system GDD
Draft: Show the draft to the user for review (never save directly)
Iterate: Apply feedback, present updated draft
Approve: User confirms; save to design/gdd/
Update Index: If a new system, update design/gdd/systems-index.md

After creating any GDD:

Run /design-review to validate quality
Update design/gdd/systems-index.md if a new system was added
Link related GDDs (combat GDD references weapons GDD, etc.)

이 저장소의 다른 Skills

같은 저장소

doctor

CodePhobiia/claude-roblox-game-studio

Run a comprehensive health check on the repo. Verifies README counts match reality, promised files exist, no unresolved placeholders, wiki index is synced, toolchain configs are valid, and agent roster is accurate. Use after making structural changes or before publishing.

2026-04-168

start

CodePhobiia/claude-roblox-game-studio

Begin a new Roblox game project or onboard to an existing one. Use when starting a fresh session with no context, or when the user says "let's start" or "new project".

2026-04-168

asset-from-image

CodePhobiia/claude-roblox-game-studio

Generate a 3D asset from a reference image using Blender MCP's image-to-3D AI (Hyper3D). Optimizes for Roblox and exports FBX.

2026-04-168

generate-asset

CodePhobiia/claude-roblox-game-studio

Generate a 3D asset for Roblox using Blender MCP. Creates models from text descriptions via AI (Hyper3D/Hunyuan3D) or downloads from PolyHaven/Sketchfab, optimizes for Roblox constraints, and exports FBX.

2026-04-168

studio-inspect

CodePhobiia/claude-roblox-game-studio

Inspect the current Roblox Studio state via MCP. Verifies instance hierarchy, checks for common structural issues, and reports findings.

2026-04-168

studio-screenshot

CodePhobiia/claude-roblox-game-studio

Capture a screenshot of the current Roblox Studio viewport and analyze it. Use for visual verification of UI, lighting, level layout, and general game appearance.

2026-04-168

/gdd — Game Design Document Workflow

If no argument provided (Master GDD):

Create the master GDD at design/gdd/master-gdd.md using the template at .claude/docs/templates/gdd-master.md.

The master GDD must include:

Game Overview: Concept, genre, platform (Roblox), target audience

Creative Pillars: 3-5 pillars that guide all decisions

Core Loop: 30-second, 5-minute, session, and meta loops

Systems Overview: List all game systems with 1-sentence descriptions

Player Progression: How do players grow over time?

Monetization Strategy: GamePasses, DevProducts, Premium Benefits

Social Features: Multiplayer, trading, guilds, parties

Target Metrics: D1/D7/D30 retention targets, session length goals

Content Plan: Launch content vs. future updates

Technical Overview: Client-server split, DataStore approach, key technical constraints

If argument provided (System GDD):

Create a system-specific GDD at design/gdd/<system-name>-gdd.md using the template at .claude/docs/templates/gdd-system.md.

Every system GDD must include:

Overview & Purpose

Core Mechanics (detailed)

Data Schema (DataStore keys, types, defaults)

Client-Server Split (what runs where)

RemoteEvents/Functions needed (with argument contracts)

Player-Facing UI (mockup or description)

Edge Cases & Error States

Balancing Parameters (formulas, not magic numbers)

Integration Points (dependencies on other systems)

Workflow Steps

Ask Context: "Are you creating a new GDD or updating an existing one?"

Delegate: Route to game-designer agent for master GDD, or systems-designer for system GDD

Draft: Show the draft to the user for review (never save directly)

Iterate: Apply feedback, present updated draft

Approve: User confirms; save to design/gdd/

Update Index: If a new system, update design/gdd/systems-index.md

After creating any GDD:

Run /design-review to validate quality

Update design/gdd/systems-index.md if a new system was added

Link related GDDs (combat GDD references weapons GDD, etc.)

name	gdd
description	Create or update a Game Design Document. Use for master GDD creation, system-specific GDDs, or GDD review. Invoke with /gdd [system-name] for a specific system, or /gdd for the master document.