frontmatter PAR AVION

Instructions

Instructions CLAUDE.md Vendor docs

config

name type required meaning concept
@path/to/import string
CLAUDE.md files can import additional files using `@path/to/import` syntax. Imported files are expanded and loaded into context at launch alongside the CLAUDE.md that references them. Imported files can recursively import other files, with a maximum depth of four hops.
docs ↗
AGENTS.md path
Claude Code reads `CLAUDE.md`, not `AGENTS.md`. If your repository already uses `AGENTS.md` for other coding agents, create a `CLAUDE.md` that imports it so both tools read the same instructions without duplicating them. You can also add Claude-specific instructions below the import. Claude loads the imported file at session start, then appends the rest:
docs ↗
CLAUDE.local.md path
For private per-project preferences that shouldn't be checked into version control, create a `CLAUDE.local.md` at the project root. It loads alongside `CLAUDE.md` and is treated the same way.
docs ↗
CLAUDE.md path
Claude Code loads `CLAUDE.md` and `CLAUDE.local.md` from your current working directory and every directory above it. Run Claude Code in `foo/bar/` and it loads instructions from `foo/bar/CLAUDE.md`, `foo/CLAUDE.md`, and any `CLAUDE.local.md` files alongside them.
docs ↗
Local instructions path
Personal project-specific preferences; add to `.gitignore`: `./CLAUDE.local.md`
docs ↗
Managed policy path
Organization-wide instructions managed by IT/DevOps: • macOS: `/Library/Application Support/ClaudeCode/CLAUDE.md` • Linux and WSL: `/etc/claude-code/CLAUDE.md` • Windows: `C:\Program Files\ClaudeCode\CLAUDE.md`
docs ↗
Project instructions path
Team-shared instructions for the project: `./CLAUDE.md` or `./.claude/CLAUDE.md`
docs ↗
User instructions path
Personal preferences for all projects: `~/.claude/CLAUDE.md`
docs ↗