game-architecture
Skill27 starsChanged 2 months agoMITView on GitHub
Code structure for games that keep growing - composition over inheritance, state machines, event bus, save systems. Use when adding a feature keeps breaking unrelated ones, or before committing to a data model.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- OpusGameLabs/game-creatortheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- OpusGameLabs/game-creator★ 360same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- craftSkill
- game-audioSkill
- game-axiomsSkill
- game-feelSkill
- game-mechanicsSkill
- game-narrativeSkill
- game-onboardingSkill
- game-playbooksSkill
- game-qualitySkill
- gameSkill
- objectSkill
- skillsSkill
- threeSkill
- worldSkill
The file
Files
architecture/ — structure that survives the fifth feature
Small games don't need this. Reach here the moment a new feature starts breaking an old one — or before you decide what a save file contains, because that decision is expensive to change later.
| page | what it fixes |
entity-composition.md | class Snake extends Enemy extends Entity — build component bundles instead |
state-machines.md | behaviour spread across a pile of if/else — model it as an explicit FSM |
event-bus.md | "enemy dies" hard-wired to score + sfx + drop + achievement — emit, subscribe |
save-systems.md | save bolted on at the end — it shapes the data model, so decide on day one |
Engine-level performance (pooling, spatial partitioning, timestep, update order)
lives in skills/three/, not here.
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.