# EngineForge Blog

> Read first-hand EngineForge workflows, product evidence, implementation explanations, and release analysis.

Canonical HTML page: https://engineforge.ai/blog

This markdown is a representation of that page for agents. Site: EngineForge (https://engineforge.ai).

## What this page is for

Discover EngineForge engineering scenarios, product explanations, and release analysis.

## Articles

- [Why Game Development AI Needs Engine Context](https://engineforge.ai/blog/why-game-development-ai-needs-engine-context): How code, editor and scene state, and runtime evidence answer different parts of a game-development task.
- [A Unity AI Workflow from Request to Runtime Verification](https://engineforge.ai/blog/unity-ai-workflow-from-request-to-runtime-verification): A first-hand Unity workflow from task planning and editor actions through runtime evidence, correction, and diff review.
- [A Godot AI Workflow from Scene Tree to Runtime Verification](https://engineforge.ai/blog/godot-ai-workflow-from-scene-tree-to-runtime-verification): A first-hand Godot workflow connecting scene, node, and script work to runtime-probe evidence and final review.
- [How the EngineForge Crew Delegates Game-Development Work](https://engineforge.ai/blog/how-engineforge-crew-delegates-game-development-work): A first-hand explanation of Maestro coordination, bounded specialist tool calls, returned verification evidence, and review.

## Related pages

- [AI Game Development Software](https://engineforge.ai/): Build Unity and Godot games in a complete AI platform with an extensible specialist Crew, runtime verification, and reviewable changes.
- [AI Assistant for Unity Game Development](https://engineforge.ai/unity-ai-platform): Work in existing Unity projects with project context, editor actions, runtime evidence, specialist Crew roles, and review controls.
- [AI Assistant for Godot Game Development](https://engineforge.ai/godot-ai-platform): Work in existing Godot projects with scene, node, and script context, runtime evidence, specialist Crew roles, and review controls.
- [AI Agents for Game Development](https://engineforge.ai/crew): Use Maestro to coordinate serial specialist tools, specialist-owned verification, sanity checks, and conditional independent testing.
- [EngineForge Documentation](https://engineforge.ai/docs): Navigate setup and usage documentation for Cockpit, Crew, Unity, Godot, runtime verification, and review controls.

## Machine-readable resources

- [llms.txt](https://engineforge.ai/llms.txt): Entry point for agents: what EngineForge is, when to reach for it, and every other machine-readable file.
- [Agent instructions](https://engineforge.ai/agent-instructions.md): When to use EngineForge, which questions it answers, and how to call the public API to answer them.
- [OpenAPI description](https://engineforge.ai/openapi.json): OpenAPI 3.1 description of the public EngineForge API, with an operation id, typed parameters, and a response schema for every endpoint.
- [Developer resources](https://engineforge.ai/developers): Human-readable index of the EngineForge public API, machine-readable files, and integration notes.
- [Documentation](https://engineforge.ai/docs): Product documentation for Cockpit, Crew, Unity, Godot, runtime verification, and review controls.
- [Sitemap](https://engineforge.ai/sitemap.xml): Every indexable EngineForge page with its last modification date.
- [robots.txt](https://engineforge.ai/robots.txt): Crawl boundaries and the canonical sitemap location.