game-designer

A Game Design Document provides a structured approach to building system architectures, ensuring coherent loops, balance, and emergent gameplay. It is needed when scattered systems thinking must be formalized into a living, modular GDD for cross-disciplinary teams during pre-production or live iterations.

Designing a balanced game economy requires producing a Core Loop Definition, Balance Spec, and Economy Health Dashboard. This enforces data-driven tuning and explicit failure states, supporting rapid prototyping and iteration for progression and economy systems in any engine.

Yes, this approach is applicable during pre-production through live iterations. It supports designing emergent gameplay by maintaining a living, modular GDD that enforces data-driven tuning and structured handoffs for ongoing balance and progression updates.

The best way to structure onboarding flows and system architectures is to use modular documentation templates. This skill specifies robust architectures and generates collaboration templates that ensure structured handoffs and coherent onboarding design across the project lifecycle.

Yes, this game design documentation method works for any engine. It focuses on engine-agnostic system architectures, producing core loop definitions, balance specs, and economy dashboards that enforce data-driven tuning without relying on specific engine dependencies.