Engineering
Give your bot the map before the files: Graphify + Obsidian
On a big folder, the bot rereads everything at the start of every session.
What hurt
Brian Roemmele (@BrianRoemmele) uses Graphify (open source) to turn a project folder into a knowledge graph and makes his bot read the report first. He notes Graphify's own token-saving claim is someone else's measurement, not his. Not affiliated with xAI.
What to install or create
Graphify parses code locally (tree-sitter) and extracts notes and PDFs, producing GRAPH_REPORT.md and a graph file. Obsidian can show the map; the bot only needs the report in its files and one line in its brief: read the report before you open a file. Each session starts with what the graph says a task touches, then opens only that cluster. Rebuild when a file's hash changes.
Bots
Project bot
Reads GRAPH_REPORT.md before opening files.
Plugins
None on day one. Follow the first-run steps.
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/BrianRoemmele/status/2108206604458111083 (credit @BrianRoemmele).
- 2Run Graphify on the project folder your bot maintains.
- 3Put GRAPH_REPORT.md and the graph file in the bot's files.
- 4Add one line to its brief: read the report before you open a file.
- 5Rebuild the graph when files change, and check misses against the edges.
Approval fence
Read-only on your files. Notes and PDFs go through an extraction pass, so keep sensitive documents out of the folder you graph.
What to tweak
Build the map once, make the hire read the map, rebuild on change.
Source
Brian Roemmele @BrianRoemmele · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.