The working context
What a session working in your repository reads before it starts: the discipline the framework is built on and how work is done with it. A repository obtains it by coordinate – impl-tool:context, named under vendoredLibraries in the configuration the dev command reads – and dev vendor unpacks it into the directory its vendorPath names. That is .claude/ unless the repository’s vendoredLibraries entry states another vendorPath, as a repository whose agent harness reads its context from somewhere else does; what follows calls it the context directory.
Nothing here is compiled. These are documents, read as written, so they are kept to what is true in any repository built on the framework.
What is here
instructions/– the working discipline, split by the question each document answers.Philosophy.md– the design discipline and its reasoning: what earns an abstraction, what a dependency costs, when to declare rather than code. The why the other three cite.workflow.md– how work is done: the verification gate, which tests a change owes, how much a session decides without asking, and fixing what the work finds rather than deferring it.tools.md– what to invoke and how: thedevcommand, pkgmgr, impl-tool, and the gotchas that belong to a tool rather than to a repository.conventions.md– what a finished thing looks like: module structure, the documentation set, the shape of a CLI application.
Making the documents reachable
A harness loads one file – your repository’s main context file – and nothing else, so a document that file does not reference is one no session opens. Open that file with a table of contents into the context directory’s instructions/, and continue it with what your repository alone answers for: its commands, its layout, its gotchas. A rule a session can be pointed at here is not restated there; restating it is how a second, staler copy appears.
The language half of the discipline is not here. A rule that is true in every repository of one language belongs with the repo adapter that implements the language, and is read from that adapter’s own INSTRUCTIONS.md.
What a session writes here
An agent harness may keep its own local state in the context directory too – settings, session records. dev vendor takes back only what it unpacked there the time before, so what a session wrote is left alone, and the directory is git-ignored in a repository that vendors this package.