agentleFS
mementomori-comementomori-co/maker-mastery/.claude/skills/gdd/SKILL.md

gdd

Skill2 starsChanged 25 days agoMITView on GitHub

Use when a game or mini-game needs a design document a second person could build from without questions. Runs the game-director in a fresh context and writes a one-page GDD to game\gdd.md in the project folder.

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

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Read lessons\INDEX.md and any game-design notes in knowledge\ (a missing folder means no verified note yet).

    line 15
  2. Distinctive:

    Write the one-page GDD: pitch, pillars (3), core loop, mechanics and systems, controls (per player: buttons, sticks, counted separately), …

    line 16
  3. Distinctive:

    Run the test: read the GDD as a stranger.

    line 19

“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

Overview

Design: $ARGUMENTS, three fields separated by |: project folder, one-line pitch, target (PC, web, a retro-emulation cabinet, or "undecided"). Output: <project folder>\game\gdd.md (see templates\project\ for the folder layout).

When to use

A new game idea, a mini-game for a printed cabinet or toy, or a redesign that needs a written target before art, code or hardware starts. Not for an animatic or storyboard alone (ask the game-director directly for a pre-production brief).

Steps

  1. Read lessons\INDEX.md and any game-design notes in knowledge\ (a missing folder means no verified note yet). Ask the lead for the project's style guide path; if none, write "style guide: none yet" in the GDD.
  2. Write the one-page GDD: pitch, pillars (3), core loop, mechanics and systems, controls (per player: buttons, sticks, counted separately), win/lose and session length, scope (must / should / cut), art and audio direction (reference the style guide, not restated), platform and engine decision, risks, open questions.
  3. Engine section: check what is installed before writing any engine step. Quote licence terms only from https://www.unrealengine.com/license, https://unity.com/pricing, https://godotengine.org/license/ fetched this run, with the page date; otherwise write not verified.
  4. Audio section: one row per planned sound class with licence source; middleware terms from the vendor page fetched this run or not verified.
  5. Run the test: read the GDD as a stranger; every place a builder would have to ask becomes a numbered NEEDS MAKER question at the end.
  6. Any fact fetched this run goes to research\inbox\<topic-slug>\<question-slug>.md in the researcher's claims-table format for /verify.
  7. Return the GDD path, the inbox paths, the NEEDS MAKER list, one next step.

Common rationalizations

RationalizationReality
"The mechanic is standard, no need to spell out controls."Players, buttons and inputs are separate counts; implicit assumptions are where builds fail.
"Godot is MIT, that never changes."Quote the licence page fetched this run with its date, or mark not verified.
"I'll describe the look here to save a hop."Look and voice belong to the style guide; reference its path, do not restate.

Red flags

  • A licence or fee without a URL fetched this run.
  • An engine step written as if the engine were installed when it was not checked.
  • Open design choices buried in prose instead of listed as NEEDS MAKER.
  • Controls section with one combined number for players and buttons.

Verification

  • <project folder>\game\gdd.md exists with all sections from step 2.
  • Every external fact carries a fetched URL or not verified.
  • NEEDS MAKER list present (may be "none" only if a stranger read-through found no gaps).
  • Claims written to research\inbox\, paths returned.

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.