# Game Foundations

> Set or repair engine-independent game architecture, including runtime choice, simulation and presentation ownership, input, assets, save data, debugging, and performance boundaries.

- Skill: `whitetowerai/game-foundations` (Agent Skill)
- Install (CLI): `npx get-skill add whitetowerai/game-foundations`
- Raw SKILL.md: https://api.skillmd.com/api/skills/whitetowerai/game-foundations/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: WhiteTowerAI (https://skillmd.com/u/whitetowerai)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/whitetowerai/game-foundations

---


# Game Foundations

Use for architecture decisions and changes crossing several game systems. Preserve the existing engine and working boundaries unless the requested outcome requires a change.

## Choose The Runtime

Start with the target platform, distribution, camera, primary actions, asset needs, and existing project. Respect an explicitly chosen engine. For an unspecified new game, choose a runtime that fits those requirements and available tooling; do not select a browser stack solely because the workspace offers Web previews. Keep the choice proportionate to the game.

## Stable Boundaries

- Simulation owns rules, entities, progression, timers, and saveable state.
- Presentation adapts that state into scenes, cameras, animation, audio, particles, and UI.
- Map supported input devices to named game actions in one place. Gate gameplay input while menus and dialogs are active.
- Use stable asset keys and a deliberate loading/import pipeline instead of scattering file paths through gameplay logic.
- Save serializable state with the project's versioning conventions, rather than renderer or engine objects.
- Keep diagnostics easy to disable, and clean up replaced resources, listeners, and subscriptions through the engine's lifecycle.

Use these boundaries in proportion to the project. Follow framework-specific ownership rules, such as Playable Nodes state and navigation, when the project already has them.

## Before Implementation

For a new or substantially changed game, establish the core loop, success/failure/restart, camera and controls, state ownership, asset loading, UI surfaces, saving, and performance expectations. Keep gameplay legible: persistent HUD should support current decisions, protect the main action area, and put secondary information in contextual or pause surfaces.

Preserve approved visual direction, sprite anchors, model units, and asset naming in focused changes. Size and optimize resources for their actual use. Measure a reported bottleneck before introducing pooling, compression, LODs, or architectural changes.

Once the required boundaries are clear, continue implementation with the chosen engine's conventions and any relevant available specialist workflow.

