What Context files is for
Context files are a good place for instructions a project should carry into future sessions: where outputs belong, how to run checks, what needs approval, and which sources are authoritative. Official documentation describes several supported filenames and precedence rules. It also distinguishes global personality from project instructions. Keep the project file short enough to guide work, and link to detailed references rather than reproducing an entire manual.
What you need
- A known working directory and the correct repository or project boundary.
- Permission to edit the intended instruction file without changing unrelated shared or global configuration.
Set it up
- 1
Inspect existing context files first and determine which type Hermes actually selects; similarly named files do not necessarily combine.
- 2
Write concrete rules with examples of valid output and necessary checks. Separate durable conventions from dated task status and record the owner of exceptions.
Check it works
- Start a session in the project and ask Hermes to identify the active instruction source and its relevant rules.
- Try a small scoped task and inspect whether output location, terminology, and verification match the instructions.
Limits and failure points
- Instructions influence behavior but are not a filesystem access control mechanism.
- Discovery and precedence depend on location and file type. Global personality settings should not be used as a hidden substitute for project-specific operating rules.
Primary sources
Spotted something wrong or out of date? Tell us on X at @HermesWatcher (opens in a new tab) and we will fix it.