An agent instruction file gives a coding agent concise project-specific direction that cannot be inferred safely from source alone. It can define scope, approval boundaries, naming, architecture, security rules, required checks, documentation duties, and how narrower directory instructions inherit or override broader ones.
The file should contain durable guidance rather than temporary plans or duplicated implementation detail. It must be maintained with the project, kept internally consistent, and written so that a future agent can verify requirements through current source and executable checks.
Acronyms and aliases
project agent guide synonymAGENTS.md variant
Related terms
Frequently asked questions
What belongs in an agent instruction file?
Include durable scope, safety, approval, architecture, naming, workflow, verification, documentation, and repository-specific constraints.
Should an agent instruction file describe every implementation detail?
No. Details that can be inspected from current source should remain there so the instruction file does not become a stale duplicate.
