agentleFS
mtarcuremtarcure/claude-vibe-squad/.agents/skills/game-design-fundamentals/SKILL.md

game-design-fundamentals

Skill220 starsChanged 20 days agoMITView on GitHub

Use when shaping a new playable concept before downstream production—state the player fantasy and experience pillars, then define core/session/meta loops, verbs, goals, obstacles, resources, and win/lose/progression conditions as the authoritative upstream brief. It chooses what play is; later specialists quantify, stage, and implement it.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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:

    Write the result as a contract downstream specialists consume (level-design-patterns, narrative-structure, game-mechanics-balancing).

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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

Game Design Fundamentals

Turn a game concept into a design contract: core loop, player fantasy, goals/obstacles, and the experience pillars everything else serves.

Steps

  1. State the player fantasy and the experience pillars (3–5) the game must deliver.
  2. Define the core loop (the moment-to-moment action → reward → motivation cycle) and the session/meta loops around it.
  3. Specify goals, obstacles, and the resources/verbs the player uses to act on the world.
  4. Define the win/lose/progress conditions and how difficulty and mastery evolve over time.
  5. Write the result as a contract downstream specialists consume (level-design-patterns, narrative-structure, game-mechanics-balancing); flag anything requiring engine support to game-engineer.

Acceptance

  • The core loop is explicit and tied to the stated player fantasy/pillars.
  • Goals, obstacles, and player verbs are named, not implied.
  • The output is a contract the level/narrative/balance specialists can build against.

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.