Installing any host seeds ~/.cues/ with a working set of cues and blanks, so the first keystroke after install already has spelling and the lookups behind it, and formality rewrites on the surfaces the cue allows. The files are yours from that moment: plain markdown, editable with anything.
| Kind | What you get |
|---|---|
| cues | spelling (the catch-all corrector), formality rewrites for whole sentences, a calendar-conflict flag, and per-host tip packs for Claude Code, OpenCode, Gemini CLI and the shell |
| blanks | volume and brightness (live device control), weather, stocks, crypto, dictionary, countries, Hacker News, places, notes, the model readout, and the settings blank itself |
| auditors | a grammar auditor on by default, a clarity auditor shipped off, and their master file |
| settings | OPENCUES.md, the runtime settings file every host reads |
| templates | a commented-out identity file, and worked examples to copy when writing your own cue or blank |
Seeding never overwrites a file you have touched.
The seed step copies a file only when it is missing (or empty, which would break the settings reads). Edit any seeded cue and the edit stays through every reinstall. The one exception is library scripts, the helpers behind blanks like volume and brightness: those resync on every install so fixes reach you, while the .md files describing them are never overwritten.
Everything is under ~/.cues/: one folder per cue under cues/, one per blank under blanks/, each with its own markdown file and any script beside it. Changes are picked up within about two seconds of saving; no restart. The browser extension gets the cues and blanks baked into its build, filtered to what a browser can run (the per-terminal tip packs stay out), so it works before the sync host is installed.
A new cue is one folder with one file: copy the shipped example under cues/example/, rename it, and write the prompt. The same shape works for blanks, with a script beside the file if the blank runs one. Cues and blanks that work in ~/.cues/ work identically in a project's own .cues/ folder; the settings file is read from the user level only.