TEMPLATE

Game UI Style Guide Template

Create a living reference for visual rules, shared components, and implementation decisions.

Why it matters

As a game grows, several designers and engineers build screens from the same parts. Without a shared reference, buttons drift in size, states behave differently, and new screens slowly lose consistency. A style guide records the rules and the reasons behind them, so the team can make decisions quickly and new members can contribute without guessing.

Foundations to copy

Record project and platform, target resolution and scaling rules, grid and safe area, type roles and example strings, semantic colors with their uses, spacing scale, icon sizes and stroke rules, and motion timing with reduced-motion behavior. Include common UI surfaces and one example of each rule.

Component entry to copy

Name [ ]; purpose [ ]; anatomy [ ]; variants [ ]; default, focus, hover, pressed, selected, disabled and loading states where relevant [ ]; supported inputs [ ]; longer text behavior [ ]; implementation notes [ ]; owner and review date [ ]. Example: Primary Button uses a visible focus outline, supports controller confirm, expands for longer labels, and keeps its focus indicator visible when selected.

Review before handoff

Build one sample settings screen from the component set. Check state consistency, scaling, contrast in context, and the relationship between token names and engine or design-file properties. Mark exceptions and explain when they apply.

Common mistakes to avoid

Documenting only how components look and not how they behave. Skipping focus, disabled, and loading states. Listing colors without saying what each one means. Letting the guide fall out of date after a few sprints. Building tokens in the design file that have no matching property in the engine.

Use it in your portfolio

Show a page or two of your style guide alongside the screens built from it. Point out one rule that solved a real problem, such as a focus style that stays visible on bright backgrounds. It signals that you can design systems, not just single screens.

Keep going

Pair this with the Engine Handoff Checklist and the Typography and Icon Audit, or practice on a real brief in the Bi-Monthly Challenges. Want feedback from working game UX/UI designers? Explore the UI Peeps Masterclass.

Copyright 2026