Agent Context Files

Create concise context files that help coding agents understand a repository without flooding every session with stale or low-value instructions.

Core Principles

1. Less is more: keep the always-loaded file short, ideally under 100 lines and usually under 300.
2. Answer WHAT, WHY, and HOW: project purpose, structure, stack, and verification commands.
3. Use progressive disclosure: link to detailed docs instead of copying them into the context file.
4. Prefer pointers over snippets: reference real files and commands that stay maintained by the project.
5. Avoid policy duplication: do not restate linter, formatter, or test rules that the tooling already enforces.

Workflow

Create A New Context File

1. Identify the target runtime or file name from the user's request.
2. Explore the repository structure and existing docs.
3. Identify the tech stack, project purpose, key directories, and common commands.