What problem does it solve? AI coding agents working on Summer Engine game projects often skip the right skill, edit scene files directly, or misuse MCP tools, causing broken scenes and inconsistent results. This Skill forces a session bootstrap that routes every request through the correct Summer skill or summer_* MCP tool before any response. ## Core Features & Use Cases - Skill routing discipline: Defines a mandatory check-then-invoke rule so the agent loads the relevant Summer skill (brainstorm-game, debug, fps-controller, gdscript-patterns, and more) before acting. - MCP usage guidance: Explains how to drive the running Summer Engine via summer_* tools on localhost:6550 instead of hand-editing .tscn files, plus recovery steps when the engine is not running. - Library discovery: Shows how to query summer_search_library and summer_read_library to find the right skill, tool, template, or reference for a task. - Use Case: A user asks their agent to add an FPS controller; the agent first loads scene-composition and fps-controller skills, then uses summer_add_node and summer_set_prop against the live engine rather than editing files. ## Quick Start Start a conversation in a Summer Engine project and let the agent load this bootstrap skill before answering any game-development request.