# Prompt templates agent guide
These Markdown files become provider-visible instructions, not user-facing help pages.
## Where to look
| Main behavior | `system.md` |
| Bounded tool-use guidance | `tools.md` |
| Skill availability | `skills.md` |
| Child-agent availability | `subagents.md` |
| Continuation summary | `compact.md` |
| Internal image request | `view_image_system.md` |
| Built-in tool descriptions | `tools/*.md` |
## Local contracts
- Keep `{{SKILLS_LIST}}` and `{{LIST_SUBAGENTS}}` aligned with their runtime substitutions. Availability wrappers are distinct from individual tool descriptions.
- `tools.md` contains tool-use guidance; it is not an automatically generated schema inventory.
- `../src/tools/descriptions.rs` includes the individual tool descriptions. Public research and direct URL fetching use `web` search/open; `read` handles local/internal resources only. Browser and ax extraction are not built-ins.
- Exact tool names, arguments, limits, and routing advice must match `../src/tools/capability.rs`, `../src/tools/args.rs`, `../src/tools/exa.rs`, and dispatch behavior. Prose must not promise unsupported operations.
- Keep compaction headings and continuation requirements deliberate: preserve relevant decisions, evidence, loaded skills, blockers, and next actions without copying whole skill bodies or reinjected context.
- Keep vision instructions separate from ordinary agent templates; they serve an internal image request.
- Do not duplicate full schemas in wrappers or add local display state to provider text.