Context Files
Reliant discovers two context files in your project root:| File | Purpose | Git Status |
|---|---|---|
reliant.md | Project context — shared guidelines, architecture notes, conventions | Commit to repository |
reliant.local.md | Personal context — your local notes, preferences, shortcuts | Add to .gitignore |
What to Include
Project Context (reliant.md)
Include information that benefits everyone working on the project:
Personal Context (reliant.local.md)
Include your personal preferences and local setup details:
Auto-Discovery
Reliant searches for context files in:- Your project root directory
- Parent directories (for monorepos)
reliant.mdfrom rootreliant.local.mdfrom root
[!TIP] Monorepo tip: Place areliant.mdin your monorepo root with shared context, and additionalreliant.mdfiles in each package for package-specific context.
Best Practices
Keep it concise — Context files are included in every conversation. Large files consume tokens without proportional benefit. Update regularly — As your project evolves, keep context files current. Outdated information is worse than no information. Separate concerns — Put team knowledge inreliant.md, personal preferences in reliant.local.md.
Use structure — Headings and bullet points are easier to scan than prose.
Avoid secrets — Never put API keys, passwords, or sensitive data in context files.
Global Context
You can also add global context that applies to all projects. Create areliant.md file in your global config directory:
Related Topics
- Model Configuration — Configure models and providers
- MCP Servers — Extend capabilities with external tools
- Custom Workflows — Create specialized workflows