Why “system” is not a synonym for “style guide”
In many studios, a design system is a Figma file that describes buttons. In a game, that is a thin slice. A true game design system also names how time behaves: how long a “short” stun is, when audio ducks under UI, and what color language means in moments of success versus recovery. The goal is not rigidity, but a shared contract so a level designer, an engineer, and a sound person can point at the same problem without talking past one another. Without that, each discipline improvises, and the player feels a subtle inconsistency they might call “jank” even if they are not sure why the word applies.
We treat system building as a translation layer between the fiction of a world and the reality of a phone. A fantasy story might need ornate borders, but the tap targets do not get smaller just because a castle has spires. The system decides how ornament sits relative to a thumb’s arc, not whether ornament exists. That distinction matters because mobile play often happens in short bursts, when attention is a finite liquid you cannot pour back into a cup after spilling. If the interface asks for two different kinds of mental effort in adjacent screens, you have broken the system even if the colors match.
Tokens that behave like game verbs
Tokens—spacing units, type ramps, and color roles—are familiar from product design, but in games we extend them to “moment tokens” as well. How many milliseconds does a “snappy” button live for? How much screen shake is “mild” versus “catastrophic”? A small studio might not formalize this on day one, but if you are six months in and still describing animation as “a bit bouncy,” the lack of a token is costing you testing time. The team argues in circles, players receive uneven feedback, and the bug tracker fills with the phrase “not sure if intended.” A moment token is not a cage; it is a tuning knob everyone can read.
Cross-discipline invariants
The cheapest failures happen when a mechanic changes but the art pipeline still exports assets at a scale meant for a previous combat model. A design system in our sense includes a living note about invariants: what a unit of distance means in a level, how UI scale relates to a safe area on a notched display, and what “horizontal vs vertical mode” is allowed to break. The point is to stop accidental drift. A narrative beat that suddenly demands a full-screen modal might be beautiful in isolation, but it also interrupts a loop that a player with one hand on a strap might have practiced for a week. We are not against drama; we want drama chosen with eyes open.
Documentation you will actually reread
We encourage teams to keep “developer notes in the open.” Not a 200-page PDF nobody opens, but a few structured pages: one for timing language, one for resource naming, and one for edge cases in accessibility. A designer who reads the accessibility page before sketching a minigame will still invent freely, but they will not invent a color-only puzzle on day thirty-five that forces a last-minute retune. A studio that treats documentation as a living room rather than a mausoleum keeps systems breathable. Aperture North’s own layout tries to show what we mean: calm surfaces, a clear hierarchy, and annotations that a tired reader can scan.
Where systems can harm
When a system is enforced to reduce conversation, you no longer have a system—you have a wall. A healthy process leaves room to challenge tokens when a prototype proves them wrong. The system should be updated, not quietly subverted, because subversion in production becomes tech debt in player trust. A shared rhythm of review—lightweight, not theatrical—is how systems stay honest. The alternative is a brittle set of rules that new hires learn to game instead of to respect.
If you are a student mapping your first system, start with one verb you care about—say, collect—and write down the feedback chain from intent to result. The gaps you list will be more useful than any grid template. If you are a lead, make room for the quiet note-taker: they are often the person who can see a contradiction three departments away.