Roo Code: `.roo/rules/` location, format and template

Where Roo Code reads project instructions, whether it reads AGENTS.md, and what the format allows. From the official documentation, checked Oct 7, 2026. See also Roo Code: pricing, popularity and alternatives.

Project files

.roo/rules/ for all modes and .roo/rules-<mode>/ for one mode
.roorules / .roorules-<mode> single files as a fallback
AGENTS.md at the workspace root

Global (all projects)

~/.roo/rules/ and ~/.roo/rules-<mode>/

AGENTS.md

✓ Yes, on by default (setting roo-cline.useAgentRules).

Format and limits

Project rules win over global ones; mode-specific rules come before general ones.

Sources: roocodeinc.github.io/Roo-Code/features/custom-instructions/

Templates

AGENTS.md for a TypeScript projectAGENTS.md

# AGENTS.md

## Project
One paragraph: what this repository does and who uses it.

## Commands
- Install: `pnpm install`
- Dev server: `pnpm dev`
- Tests: `pnpm test` (run before you finish)
- Lint and types: `pnpm lint && pnpm typecheck`

## Layout
- `src/app/`: routes and pages
- `src/lib/`: shared logic, no UI code
- `tests/`: mirrors `src/`

## Conventions
- TypeScript strict mode; avoid `any`.
- Follow the patterns already in `src/` before adding new ones.
- Small, focused functions; name things for what they do.

## Boundaries
- Never read or edit `.env*` files or commit secrets.
- Ask before adding a dependency or changing a public API.

## Done means
Tests pass, lint is clean, and the change is explained in the PR description.

Written by AgentGid as a starting point; swap in your own commands and folders.

Roo Code: .roo/rules/ location, format and template