Repository navigation
Commands
Wim Wessels edited this page Oct 19, 2026
·
1 revision
English | Nederlands
| Command | When | What it does |
|---|---|---|
/kennis-intro |
Once, at the start | Explains how it works, asks where the vault goes, who you are and how you organise your work, and sets everything up |
/catchup |
Start of a conversation | Reads the vault and tells you in a few lines where you were and what the next step is |
/save-context |
End of a conversation | Writes down what changed, what was decided and what the next step is |
/vault |
On its own, when the assistant works in the vault | The rules for the notebook: what goes where, what notes look like, tidying up, the weekly check |
/kennis-tooling |
During installation, or when something is missing | Helps install Python, and Node.js if you need it |
How you call them differs per program:
| Program | How you type it |
|---|---|
| Claude, as a plugin | /kennisbasis:catchup |
| Claude, via install.md | /catchup |
| Codex | $catchup |
| ChatGPT desktop | Choose the plugin and say the name: "catchup" |
You can also just say the name: "catchup", "save-context".
For the first ten times, the assistant now and then reminds you of /catchup and /save-context. After that it is a habit and the reminders stop.
A notebook gets messy if nobody keeps it up. During the intro, the assistant sets up a check that runs every week on its own, even when your AI program is closed. It updates the lists in your overview notes, repairs links and writes a short report in _Onderhoud/laatste-controle.md. Whatever it may not fix itself, /catchup mentions in your next conversation.
On the Mac this uses the built-in scheduler (launchd), on Windows Task Scheduler, on Linux cron.