agentleFS
Sign inStart free
StanestaneStanestane/game-design-skills-bundle/game-design-craft-critique/SKILL.md

game-design-craft-critique

Skill66 starsChanged 56 days agoLicence not identifiedView on GitHub

Critically analyze an existing, shipped, third-party or competitor game for craft lessons, using a layered method (adapted from Raph Koster's "How I Analyze a Game") that separates a game's systems from its surface experience, guesses the intent behind each layer, and checks whether those intents actually line up. Use this whenever the user wants to study a released game, competitor title, or reference game in depth -- not just describe it, but understand why it's built the way it is and what to steal from it. Trigger on requests like "analyze [game]", "break down how [game] works", "what can we learn from [game]", "why does [game] feel so good/bad", or "study this competitor game." This is a game-study tool aimed at OTHER people's games, distinct from the feature-pitch and own-design audits elsewhere in this bundle -- though it also works as a systems-vs-experience alignment gut check on your own game once both layers exist enough to compare.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

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.

Check your setup, free