Add project instructions with AGENTS.md
Create an AGENTS.md file at your project root. Devin CLI reads it automatically, and the file can be version-controlled and used across AI tools (Devin CLI rules).
Use project rules for coding standards, architecture guidance, preferred libraries, testing conventions, and project constraints (Devin CLI rules).
Set rules that apply across projects
On Linux and macOS, put global rules in ~/.config/devin/AGENTS.md. On Windows, use %APPDATA%\devin\AGENTS.md. Global and project rules are active together (Devin CLI rules).
For personal instructions, put AGENTS.local.md beside AGENTS.md. Devin CLI loads it alongside the project rules. Add the local file to .gitignore if it should stay private (Devin CLI rules).
Use Skills for scenario-specific guidance
Devin CLI recommends Skills instead of Rules when possible because Skills are added to context only when relevant. A rule can point to Skills for particular scenarios (Devin CLI rules).
Keep Rules and AGENTS files as small as possible (Devin CLI rules).
Choose a rule file location
Project-root rules load at session start. Rule files in subdirectories are discovered when Devin CLI accesses those directories (Devin CLI rules).
Devin CLI also reads rules from .devin/rules/ and .devin/global_rules.md. The .devin/ directory takes precedence over .windsurf/ when both provide a global rules file (Devin CLI rules).
Import rules from other tools
Devin CLI supports rule files including AGENTS.md, AGENTS.local.md, AGENT.md, .windsurfrules, and CLAUDE.md (Devin CLI rules).
You can enable or disable imports from other tool formats with read_config_from in the Devin CLI config file (Devin CLI rules).
Questions people ask
Where should I put project rules for Devin CLI?
Put them in an AGENTS.md file at the project root. Devin CLI reads it automatically, and it can be version-controlled (Devin CLI rules).
How can I make rules apply to every project?
On Linux or macOS, use ~/.config/devin/AGENTS.md. On Windows, use %APPDATA%\devin\AGENTS.md; global and project rules are active together (Devin CLI rules).
When should I use a Skill instead of a Rule?
Devin CLI recommends Skills for instructions that apply only when relevant. A Rule can point to a Skill for a particular scenario (Devin CLI rules).
Can I keep personal rules out of the project file?
Put them in AGENTS.local.md beside AGENTS.md. Devin CLI loads it alongside the project rules; add it to .gitignore if it should stay private (Devin CLI rules).