How the agent finds code
- Project Intelligence indexes your project so the agent can search it. See Project Intelligence.
- @ mentions point the agent at exact files and folders. See Working with context.
- Subagents explore and do focused work, so the main chat stays short. See How Summer’s AI agents build your game.
- Rules tell the agent your conventions in every chat. See below.
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
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.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.”

