Record what is specific to the project
I use an instruction file for things an agent cannot easily infer from the code. That includes decisions and verification commands. General requests for good code do not replace that information.
Maintain one source
When several coding tools work on a project, they should read the same rules. I keep shared rules centrally and reference them from each entry point. When changing them, I check which tools actually load the source.
Rules need enforcement
A written instruction is not an access restriction. In my agent platform, Harness, hooks enforce routing and safety rules. Daily budgets for paid calls live in the broker. Separating these responsibilities makes it clear where a limit is enforced.
Keep the file current
When the workflow changes, the instructions need to change too. I remove obsolete commands and duplicated explanations. A short, current file helps the next agent more than the full history of every earlier decision.