game-foundations
Installation
SKILL.md
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.