game-axioms
Skill27 starsChanged 2 months agoMITView on GitHub
The non-negotiables of playability - core verb, feedback latency, flow channel, meaningful choice, teaching by doing, fast retry, camera coupling. Check these when a game "works" but nobody wants a second run.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- craftSkill
- game-architectureSkill
- game-audioSkill
- game-feelSkill
- game-mechanicsSkill
- game-narrativeSkill
- game-onboardingSkill
- game-playbooksSkill
- game-qualitySkill
- gameSkill
- objectSkill
- skillsSkill
- threeSkill
- worldSkill
The file
Files
axioms/ — the non-negotiables
Everything else in game/ is taste. These seven are closer to physics: break one
and the game stops being playable, no matter how it looks. Pull the one that
matches the symptom.
| page | the axiom | symptom that sends you here |
core-loop.md | one core verb, satisfying in a 30-second isolation test | the game is only fun because of what surrounds the verb |
feedback-latency.md | keypress → any screen/speaker change under 100ms | "it feels laggy" with a fine frame rate |
flow-channel.md | challenge tracks skill; too far either way and they quit | players quit bored, or quit frustrated, both early |
meaningful-choice.md | a game is a series of interesting decisions | it plays itself; there's one obviously right move |
play-teaching.md | level design is instruction design — never a text wall | you're writing a tutorial popup |
retry-latency.md | death → back in play under 3 seconds | players stop at the death screen instead of retrying |
camera-coupling.md | camera scheme and movement scheme must be compatible | snap-turn on an orbit cam, or the player can't see where they're going |
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
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.