Word cues

Alternatives come from cue files, one per subject, under ~/.cues/cues/. Each file declares which words it matches, and every word is claimed by exactly one file.

A word is claimed by one file

Not offered to all of them and merged afterwards.

Every word in the line is matched against your files in priority order. The first file that matches a word claims it, and no other file receives it.

WordClaimed byResult
ispellingnothing to say
recievespellingreceive
tehspellingthe
contractspellingnothing to say
tommorowspellingtomorrow

This routing table was read from a running host for the line in the demo above. One shipped file matches ordinary words, so it claimed all five and returned alternatives for three.

Claiming isolates prompts

A file's instructions are only applied to the words it claimed.

Each file carries its own model instructions, sent only with that file's words. A file cannot influence a word another file claimed, because the model never sees them together.

Two consequences: one file's prompt cannot steer another's words, and a file from a third party has a visible boundary, the words it declares. A higher-priority file does claim its words away from lower ones; that is the priority number doing its job.

What ships

The shipped cue files, plus per-host tip files.

FileClaimsPriority
more-formalwhole sentences, in the shell and on allow-listed sites (LinkedIn, web email)85
calendarsentences mentioning a time, once you have added a feed90
spellinganything at all, and so anything left over10

Spelling has the lowest priority because it matches every word: any higher and it would claim words before more specific files could. At priority 10 it acts as the catch-all, which is why typos are caught in any sentence.

Adding a cue is one file

No plugin, build step, or restart.

A CUE.md declares a name, the words it matches, a priority:, and prose instructions for the model. Saving it applies within about 2 seconds.

~/.cues/cues/your-subject/CUE.md

The instructions are prose, so changing what a file suggests is editing a sentence, with nothing to compile.

Project-level and user-level files

Looked for inMeaning
<project>/.cuesthis project's own, and it wins where the two disagree
~/.cuesyours, everywhere else

A repository can commit its own .cues/ folder, so its vocabulary travels with the code and applies only inside that project.

No matching words, no request

A file with no matching words in the line generates no request. Files that claimed words each send one request, carrying only their own words.