agentleFS
CodePhobiiaCodePhobiia/claude-roblox-game-studio/.claude/skills/gdd/SKILL.md

gdd

Skill9 starsChanged 7 months agoMITView on GitHub

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.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

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

    line 9
  2. Very specific:

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

    line 24
  3. Distinctive:

    Every system GDD must include:

    line 26
  4. Very specific:

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

    line 43
  5. Very specific:

    Run /design-review to validate quality

    line 46
  6. Very specific:

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

    line 47

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/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:

  1. Game Overview: Concept, genre, platform (Roblox), target audience
  2. Creative Pillars: 3-5 pillars that guide all decisions
  3. Core Loop: 30-second, 5-minute, session, and meta loops
  4. Systems Overview: List all game systems with 1-sentence descriptions
  5. Player Progression: How do players grow over time?
  6. Monetization Strategy: GamePasses, DevProducts, Premium Benefits
  7. Social Features: Multiplayer, trading, guilds, parties
  8. Target Metrics: D1/D7/D30 retention targets, session length goals
  9. Content Plan: Launch content vs. future updates
  10. 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:

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

Workflow Steps

  1. Ask Context: "Are you creating a new GDD or updating an existing one?"
  2. Delegate: Route to game-designer agent for master GDD, or systems-designer for system GDD
  3. Draft: Show the draft to the user for review (never save directly)
  4. Iterate: Apply feedback, present updated draft
  5. Approve: User confirms; save to design/gdd/
  6. 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.)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.