ai-coders-context
AGENTS.md571 starsChanged 7 months agoMITView on GitHub
This repository exposes one runtime through four surfaces: Agents working in this repo should preserve that separation. If a change affects reusable execution logic, prefer src/harness/application. If a change affects reusable domain rules, prefer src/harness/domain. If a change affects protocol shape or request handling, prefer src/mcp/gateway. If a change affects user-facing commands or installation flows, prefer src/cli. If a change affects host event mapping or hook templates, prefer src/integrations. Do not add new code under src/services; that directory is not…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this AGENTS.md into the rules it gives an agent
7 rules. About 0 are common, 0 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
If a change affects reusable execution logic, prefer src/harness/application.
- Very specific: line 20
If a change affects reusable domain rules, prefer src/harness/domain.
- Very specific: line 21
If a change affects protocol shape or request handling, prefer src/mcp/gateway.
- Very specific: line 22
If a change affects user-facing commands or installation flows, prefer src/cli.
- Very specific: line 23
If a change affects host event mapping or hook templates, prefer src/integrations.
- Very specific: line 24
Do not add new code under src/services.
- Very specific: line 52
If you touch mcp:install, keep these aligned:
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dotcontext Agent Instructions
This repository exposes one runtime through four surfaces:
cli -> harness <- mcp
<- integrations (host hooks / extensions)Agents working in this repo should preserve that separation.
Architectural Intent
cliis the operator interfaceharnessis the reusable execution runtimemcpis the transport adapter for AI toolsintegrationsis the host hook and extension layer (Claude Code, Codex CLI, Pi)
If a change affects reusable execution logic, prefer src/harness/application.
If a change affects reusable domain rules, prefer src/harness/domain.
If a change affects protocol shape or request handling, prefer src/mcp/gateway.
If a change affects user-facing commands or installation flows, prefer src/cli.
If a change affects host event mapping or hook templates, prefer src/integrations.
Do not add new code under src/services; that directory is not part of the target architecture.
Repository References
README.mdexplains what dotcontext is and why it exists- dotcontext.dev (source in
docs/) explains how to use it ARCHITECTURE.mdexplains how the harness worksCONTRIBUTING.mdexplains contributor workflowCHANGELOG.mdtracks release-facing changes
Expected Validation
For code changes:
npm run build
npm test -- --runInBandFor packaging or release-surface changes:
npm run build:packages
npm run smoke:packagesMCP Install Changes
If you touch mcp:install, keep these aligned:
src/cli/services/mcpInstallService.tssrc/cli/services/mcpInstallService.test.tsREADME.mddocs/src/content/docs/(published at dotcontext.dev)CHANGELOG.md
Documentation must reflect the actual config written by the installer.
Hook Install Changes
If you touch hook install, keep these aligned:
src/cli/services/hookInstallService.tssrc/cli/services/hookDispatchService.tssrc/cli/services/__tests__/hookInstallService.test.tssrc/integrations/claude-code/,src/integrations/codex/,src/integrations/pi-dev/README.mddocs/src/content/docs/(installation and hooks guides)CHANGELOG.md
Documentation must reflect the actual config written by the hook installer and the Pi extension install path.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

