Skip to main content
A big project has more code than the agent can read in one turn. These habits help the Summer Engine agent find the right files and make changes that fit your project.

How the agent finds code

Get up to speed

Start with broad questions, then narrow down.

Rules for consistency

Write your conventions down once. Summer reads these files at the start of each chat: A rule file in .summer/rules/ can have frontmatter. With globs and no alwaysApply: true, the rule applies only when the chat works on matching files.
.summer/rules/combat.md
For each folder from the project root to the chat’s folder, AGENTS.md takes precedence. Summer reads .summerrules in that folder only when AGENTS.md is absent. Put shared instructions in one file per folder so both sets are not mistakenly expected to load together. For decisions about your game itself (art style, mechanics), use Memory. For a repeatable way of working, write a Skill.

Plan big changes first

Ask for a plan before the agent edits anything.
Then do the plan in steps you can test:
To approve each edit yourself, set the chat’s permission mode to Manual. Accept edits runs project edits and still asks before paid tools and commands.

Point at working examples

The agent copies patterns well. Name the file to copy.

Keep systems apart

Tell the agent what a system must not do. This stops changes from spreading.

Keep chats focused

  • Start a new chat for each feature or bug.
  • When you start a new chat, say in two or three lines what the system is and where it lives.
  • Narrow the scope: “Only change files in @ui/ for this fix.”

Debug in order

Give the error and the path the data takes.
To isolate a bug, ask for a small test scene that loads only the systems involved.