summer-engine-agent GEMINI.md

Summer — Context Primer for Gemini

Summer is the AI game-dev studio for Summer Engine — the AI-native game engine. When you see this file in a session, it means the user has installed the Summer Gemini extension and you have access to the summer-engine MCP server plus Summer skills under the summer: namespace.

What Summer Engine is

Summer Engine is designed for AI-assisted creation. The user is making a Summer game with the Summer SDK, normally in GDScript. The editor, scene graph, asset pipeline, and runtime are instrumented for programmatic control via MCP. Summer currently uses the 4.6.1 upstream technical base, plans to adopt 4.7.1 next, and follows upstream continuously. Those numbers are compatibility facts, not the product identity. Projects use GDScript (.gd), C# (.cs), scenes (.tscn/.scn), resources (.tres/.res), and the technical project.godot filename.

How to behave

Always check for a relevant Summer skill before writing code or running tools. Skills encode discipline that matters — debug protocols, scene-composition rules, GDScript idioms Gemini regularly gets wrong. If a skill might apply, even at 1% probability, activate it via activate_skill.

The single most important skill to know is summer:using-summer — it explains the workflow, priority, and the red-flag table of rationalizations the model needs to resist. Activate it first thing in any Summer Engine session.

Skill priority

1. Process skills first: brainstorm-game, debug, play. These determine HOW.
2. Discipline skills second: gdscript-patterns, scene-composition, art-direction, audio-direction. These shape content.
3. Build skills third: fps-controller, design-mechanic, design-level, setup-multiplayer, vfx, tune-performance, export-and-ship.

MCP tools (when the project-matched local editor is running)

The summer-engine MCP server exposes a focused tool registry. The most important:

• Scene mutation: summer_add_node, summer_set_prop, summer_set_resource_property, summer_remove_node, summer_save_scene, summer_replace_node, summer_batch. Every scene mutation requires the exact res://...tscn scenePath; opening a scene is a user-visible UI action, not a mutation prerequisite. Mutation tools append one final SaveScene; raw engine batches must do the same.
• Scene inspection: summer_get_scene_tree, summer_inspect_node, summer_inspect_resource.
• Diagnostics: summer_create_debug_report, summer_get_script_errors (cheapest), summer_get_diagnostics, summer_get_console, summer_get_debugger_errors, summer_get_debugger_warnings.
• Run game: summer_play, summer_stop, summer_is_running.
• Visual: summer_screenshot (capture the viewport or running game as an image you can see).
• Project: summer_get_project_context, summer_open_main_scene, summer_project_setting, summer_input_map_bind.
• Files: summer_read_file, summer_write_file, summer_replace_text (identity-bound, create-only or sha256-guarded mutations).
• Assets: summer_search_assets, summer_import_asset, summer_import_from_url, summer_generate_image, summer_generate_3d, summer_generate_audio, summer_generate_video, summer_check_job.