The right context, before the first edit.
When you ask for a change, Prepare adds the files the agent should edit, the tests that cover them, and code already in the repo to reuse. The agent starts in those files.
- src/billing/totals.ts: matches compute, total
3: function computeTotals(lines: Line[])
Tests: test/invoice.test.ts, test/totals.test.ts
Run: npx vitest run test/invoice.test.ts test/totals.test.ts
Only files it is sure of
Up to three files, each with a reason: the ones your request names, or a clear top pick. When Prism is not sure, it lists none and asks the agent to call prepare_change.
Code to reuse
Helpers that already exist nearby, so your agent doesn’t write a second copy.
Tests and the command
The tests for those files and the exact command to run them.
No repeats
Files already shown in this session are listed as “Same as before”.
Small answers
A Prepare answer fits in 2,000 tokens by default; the automatic one in 1,200.
Ranked by git history
Files that often change in the same commits rank higher.
Notes it hands back
Save a fact once with prism remember. Prepare returns it with the right file.
Try it in your repo.
Install Prism, then connect every agent on this machine. Open the agent again.