ai-coders-context
CLAUDE.md571 starsChanged 7 months agoMITView on GitHub
This repository is the source for the dotcontext runtime and its operator/adaptor surfaces. Current product shape: Do not move domain behavior into cli, mcp, or integrations if it belongs in harness. Integrations call the harness only — they never import cli or mcp. The repository now supports: When changing any of the following, keep docs in sync: At minimum, review:
In this repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Do not move domain behavior into cli, mcp, or integrations if it belongs in harness.
- Distinctive: line 53
When changing any of the following, keep docs in sync:
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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 Repository Guide
This repository is the source for the dotcontext runtime and its operator/adaptor surfaces.
Current product shape:
cli -> harness <- mcp
<- integrations (host hooks / extensions)Source of Truth
Start here:
README.mdfor product description and install guidance- dotcontext.dev (
docs/) for usage guidance ARCHITECTURE.mdfor runtime and boundary diagramsCHANGELOG.mdfor release notes
Working Boundaries
src/clicontains operator-facing exports and CLI-oriented services (sync, MCP install, hook install, admin)src/harnesscontains reusable runtime exports — domain rules, application services, and adapterssrc/mcpcontains the MCP transport boundary — server, gateway handlers, and schemassrc/integrationscontains host hook adapters for Claude Code, Codex CLI, and Pi
Do not move domain behavior into cli, mcp, or integrations if it belongs in harness. Integrations call the harness only — they never import cli or mcp.
Current Priorities
The repository now supports:
- durable harness sessions
- sensors and backpressure
- task contracts and handoffs
- policy documents and policy evaluation
- replay and failure datasets
- host hook install for Claude Code, Codex CLI, and Pi
- local packaging for
cli,harness,mcp,integrations, andpi
Validation Commands
npm run build
npm test -- --runInBand
npm run build:packages
npm run smoke:packagesDocumentation Hygiene
When changing any of the following, keep docs in sync:
- product positioning
- MCP install behavior
- hook install behavior
- package boundaries
- workflow commands
- release/versioning guidance
At minimum, review:
README.mddocs/src/content/docs/(published at dotcontext.dev)ARCHITECTURE.mdCONTRIBUTING.mdCHANGELOG.md
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.

