Local-first by default | Cloud workspaces only when you enable them | Your work is not used for training
Home / Workflows / GDD Workflow

Turn your game design document into implementation work you can review.

A GDD is useful only when it survives contact with production. Aura helps translate design notes into implementation plans, code suggestions, project rules, and engine-specific next steps so the design and the build stay connected.

This workflow is for developers who want AI help without losing the source of truth behind the game.

Aura Core supports unlimited local projects and GDDs. Choose the optional 100-request Gemini trial, Personal BYOK, or prepaid Aura Balance for eligible managed models.

What this workflow keeps visible

See the context Aura can use, the decisions that still need your judgment, and the checks to review before work changes your game.

Design source

Mechanics, entities, constraints, tuning notes, progression, UI rules, and player goals.

Project mapping

Existing systems, selected files, project rules, and likely affected areas.

Implementation plan

Small steps, affected files, risks, tests, and review points before changes land.

Living context

Rules and notes that can evolve as the prototype becomes a production project.

Why a GDD needs an implementation layer

A design document says what the game should be. The project shows what the game currently is. The hardest work often lives between those two states.

Aura helps surface that gap. Ask it what already matches the GDD, what contradicts the GDD, and what the smallest next implementation step should be.

Example GDD prompt

Prompt: "Use this GDD rule to inspect the current movement system. Tell me what already matches, what is missing, and what the smallest safe implementation step should be."

A useful answer should summarize current state, list gaps, name affected files or systems, identify risks, and propose a testable first step.

Questions a connected GDD can help answer

Ask Aura to turn one GDD section into reviewable tasks, compare a documented mechanic with the available project context, or identify the smallest testable step without treating the document as infallible.

FAQ

Can AI turn a GDD into a game?

AI cannot replace the developer, but it can help turn GDD sections into implementation plans, code suggestions, tuning checks, and task breakdowns.

How does Aura use a GDD?

Aura can reference connected design documents when you ask for GDD-aware help, using them to reason about mechanics, constraints, entities, systems, and implementation direction.

How does Aura handle GDD data?

Aura is local-first by default. Core GDD context stays on your device. Pro cloud continuity and Cloud Loops use cloud storage or processing only when you enable them, and your content is not used for training.

Related Aura pages

Start from the path that matches your game.

Build a first playable inside Aura, start a new Unity, Godot, or Unreal project, or connect the game you already have.