Skip to main content
The Summer Engine agent writes better code when it can check the docs instead of guessing. It reads two kinds: public documentation, and the docs inside your project.

What the agent can read

Agents connected through the Summer MCP can also search these docs with summer_docs_search and read a page with summer_docs_read.

Point the agent at the right docs

Name the class or page you mean:
When an answer looks out of date, say so: “Check the current API docs before you change this.”

Keep docs in your project

The agent reads files in your project, so docs you keep there help every chat. AGENTS.md at the project root. Your structure and conventions, read at the start of every chat. See Rules for consistency.
AGENTS.md
Doc comments. ## comments above a class, variable or function show up in the editor’s help, and the agent reads them with the code.
System notes. A short Markdown file per big system, such as docs/combat.md, with how data flows and which files own what.

Let the agent write and update docs

A simple team standard

Working with context

@ mentions, errors and rules

Project Intelligence

How Summer indexes your project