ai-game-designer

To convert a game concept into engineering-ready design specifications, provide the vision and constraints to generate a structured spec with defined core loops, economy sources, sinks, and validation gates. This translates high-level ideas into implementation-ready contracts.

The best way to define game economy sinks and sources is to map them within a structured design specification that enforces explicit constraints and validation gates. This ensures all economic inputs and outputs are tracked for engineering handoff.

You map game features to core loops and progression gates by applying structured constraints during the design specification process. This verifies dependencies and ensures every feature aligns with the defined retention and progression models.

Yes, you can generate a handoff-ready patch plan from a high-level game design document. The specification process validates spec integrity, verifies telemetry keys, and produces an implementation-ready mapping for engineers.

No, you do not need to start with predefined telemetry keys. The specification process actively defines and verifies telemetry requirements alongside progression gates, ensuring all necessary tracking keys are mapped before engineering handoff.