Customize
Instructions and rules
Tell the KazoCode agent how your project works with KAZO.md, AGENTS.md or CLAUDE.md, personal instructions, imports, and rules that apply only to matching files.
Instruction files tell the agent what it can't learn from the code: how to build and test, the conventions you follow, and what to avoid. KazoCode reads them at the start of every conversation. See and edit them in Settings › Rules & Memories, or with /memory.
Where instructions come from
| Scope | File | Use it for |
|---|---|---|
| Organization | Set up by your administrator | Policies for everyone on the computer |
| You | ~/.kazocode/KAZO.md | Your preferences in every project |
| Project | KAZO.md, AGENTS.md or CLAUDE.md at the project root, or .kazo/KAZO.md | Conventions shared with your team; commit it |
| Parent folders | KAZO.md, AGENTS.md or CLAUDE.md in folders above the project | Shared rules for a monorepo or a group of projects |
| Subfolders | KAZO.md, AGENTS.md or CLAUDE.md inside the project | Read when the agent works on files in that folder |
| Private | KAZO.local.md or CLAUDE.local.md | Notes just for you; add it to .gitignore |
Because KazoCode reads AGENTS.md and CLAUDE.md, a project already set up for other coding agents works in KazoCode without changes.
Writing good instructions
Keep them short and specific. The agent follows concrete rules far better than general advice.
# Acme API
- Package manager is pnpm. Run `pnpm test` before finishing a change.
- Routes live in `src/routes/`, one file per resource, validated with Zod.
- Never edit files in `generated/`; run `pnpm codegen` instead.
- Commit messages are in the imperative: "Add rate limiting", not "Added".Importing other files
Write @path/to/file to pull another file into the instructions, for example @docs/architecture.md or @~/.kazocode/style.md. Imports can nest up to five levels deep.
Rules for parts of a project
Put rule files in .kazo/rules/ (or .claude/rules/). A rule without frontmatter always applies. Add paths to apply a rule only when the agent works on matching files:
---
paths:
- "db/migrations/**"
---
Migrations are append-only. Never edit a migration that has been merged;
add a new one instead.Output styles
An output style changes how the agent writes, not what it knows. Choose one with /output-style: the default, Explanatory (explains its choices as it works), Learning (leaves small pieces for you to write), or your own style in .kazo/output-styles/ or ~/.kazocode/output-styles/.
Updated November 20, 2026