gds-generate-project-context

Run this workflow and it will scan your architecture documents, engine configs, and codebase to discover your technology stack and patterns. It then guides you through rule categories with approval menus before writing the final project-context.md file.

It should include exact technology versions, engine-specific lifecycle rules, performance constraints, code organization and naming conventions, testing requirements, platform rules, and anti-patterns to avoid. The focus is on unobvious details agents would otherwise miss.

Yes, the discovery step checks for engine-specific files like ProjectSettings, .uproject files, and project.godot, and the generation step includes tailored rule sections for Unity, Unreal, and Godot patterns as well as custom engines.

Yes, the customize.toml file supports activation step overrides, persistent facts including file references, and an on_complete hook. Team and user-level TOML overrides merge with the defaults using structural merge rules.

The discovery step detects the existing file, reports how many sections it contains, and asks whether you want to update it or create a new one before making any changes.