Mainloop links mechanics, systems, levels, tasks, and decisions in one GDD. Each module can be worked on separately or viewed inside the complete system; AI helps structure, review, and maintain consistency as the game changes.
Connected design
Each module stands alone and remains part of the systemThe same information can be reviewed as modules, relationships, coverage, and risks without leaving the GDD.Mainloop organizes design using the same categories as the app: Base, Design, Levels, and Development. Each module can evolve without forcing you to rewrite the whole GDD.
Choose a module to explore which decisions should be defined and connected.
The base that keeps concept, intent, rules, spaces, and development decisions aligned.
When a mechanic changes, systems, levels, progression, and rules may change too. If the GDD does not show those connections, the design can start breaking without it being obvious.
Mainloop helps keep those decisions connected so you can review which parts of the design are affected.
Notes, chats, documents, references, and old versions make understanding the real state of the design take more energy than designing.
Mainloop centralizes design in clear modules so the GDD stays useful during iteration.
A static GDD becomes obsolete when the design changes. If nobody updates it, it stops being a design tool.
Mainloop keeps the GDD alive, editable, and connected to the real creative process.
How it works
Start from a premise, playable fantasy, references, or a playable test.
Organize essentials, loops, mechanics, systems, levels, and open decisions into clear modules.
Review contradictions, weak links, risks, and design areas that need more definition.
Turn mature decisions into tasks, exportable context, and useful material for development.
What changes in prototype or development returns to the GDD so it stays alive.
Use one visual, modular source to align design, levels, and development.
Roles
Structure decisions, mechanics, and systems inside a Game Design Document that evolves with the game.
Organize intent, loops, mechanics, systems, and open questions without losing how each decision relates to the rest.
Connect areas, levels, blockouts, puzzles, and pacing with the rest of the GDD so every space has intent.
Receive clearer rules, dependencies, and decisions before implementing features or preparing a technical base.
Learn to document a game with practical guides, templates, and examples. Bring what you learn from prototypes and playtests back into a GDD that keeps evolving.
Learn what a Game Design Document is, what a Level Design Document is, and how to structure useful documentation.
Read the guideA visual guide for moving from an early idea to design, documentation, validation, and iteration without losing context.
A short reference for organizing intent, loops, mechanics, systems, and open decisions inside the GDD.
A compact guide for connecting areas, levels, blockouts, puzzles, and pacing with the broader game intent.
A summary for turning design decisions into rules, dependencies, and clear context before implementation.
Mainloop
01When a game grows, design becomes fragmented. Ideas stay in notes, mechanics change, systems contradict each other, and levels lose intention.
02The problem is not writing more documentation: it is keeping a clear source of decisions.
03Mainloop exists to sustain that clarity. It does not replace the designer’s judgment.
04It makes it more visible, organized, and easier to review.
The same GDD stays with the game to preserve decisions, relationships, and context.
Real processes, design decisions, and lessons from building Mainloop
These links prepare an email to support to request withdrawal from a purchase or cancellation of a subscription.
Add the information you have and send the message from your email app. The request goes to soporte@mainloop.ai.