Shorthand
Short commands and abbreviations for working with collaborator. NB: ALL urls on this page are relative to ~/GitHub/mono/
| Command | Action |
|---|---|
chime | In plain english, very briefly give observations, suggestions, corrections about the topic at hand |
claude | Reread <current-go>/CLAUDE.MD |
check | audit the memory system per the check entry in memory/shared/truth/protocol.md (Skills section). Report finding → file → fix; fix nothing unless told |
define <X> | coin or redefine term X per "Prose and terminology" in memory/shared/truth/protocol.md — lexicon entry + D: log line in one act; the lexicon's only door |
done | update code debt by moving checked off items to top of done section. simplify and tighten handoff, moving done things to work journal. update work journal, working features, and map |
egads | Jonathan is extremely disappointed and has far less trust that collaboration can succeed |
explain | produce analysis only. Do not touch code, nor propose changes, nor fix problems, nor start the next task. Stop after the analysis and wait for the next instruction |
fix | analyze explanation of a bug, and precisely fix it |
geometric | use names of SO rather than obj_N, use label names of eps when describing faces, segs or eps |
go | proceed with proposal as stated |
guide <X> | follow instruction steps 2 and 3 in [[add a guide]] for file X |
half | The last reply ran long. Send it again at half the words, saying the same thing |
help | Show this table |
learn, decision | Summarize the mistake you just made, add it to learn, and report number of pending entries |
memory | Describe any useful auto-generated insights from userMemories (normally ignored?) |
mothball | state and confirm the specifics of the current context. then gather everything relevant into a mothball file |
murky | carefully review the chat so far |
pause | add the current context to the current project's [[current context]] |
plain | translate using only plain english and our lexicon. do not use technical or mathematical terms without first defining them. offering to add them to our lexicon |
propose, proposal | describe your plan and do NOT execute it |
rate | read .claude/hooks/murk.jsonl. report complaints per 100 replies, and the change since the last time it was asked. then append a new line to ov/notes/work/murk.md -> date, replies, complaints, rate |
review <X> | (X is a file name, line number, Jonathan's correction or the chat so far). analyze X (original and correction) and write an instruction that, when applied by you to the original, produces the correction |
setup | for the current project, create whatever notes/work/now/ files are missing per the minimal set in notes/guides/collaborate/workflow.md: always add code debt.md, handoff.md. add the rest only when asked. NEVER overwrite an existing file; report what got created |
settle | consolidate the active project's log per "Consolidation" in memory/shared/truth/protocol.md — all five steps; finish with the settle manifest (each line and where it went) |
shorthand | Read this file (shorthand.md) |
start | orient per "Session protocol" in memory/shared/truth/protocol.md: root index → protocol → project index → lexicon → matched truths. Reply with the three-line orientation |
simplify | say the last reply again with fewer moving parts: fewer clauses, fewer names, one idea per sentence |
tokens | crude (rough, loose) estimated percentage of context consumed (okay with me that no exact measurement is available, just give me a number) |
translate, rewrite | Rewrite the last response using concise, plain english. Avoid jargon. |
undo, revert | Revert last file change |
where <X> | name the one file that owns X, per "Finding where to tweak" in memory/shared/truth/protocol.md; two claimants = duplication bug, report both |
circles | abort this task, summarize the work in 'aborted.md' begin an an breakdown |
Abbreviations
| Abbreviation | Meaning |
|---|---|
cd | read code debt.md |
dev | read all md files in notes/guides/develop (in both mono and <current-go>) |
ex | Execute mode — skip proposals, just do it |
loc ... | what is the line of code for determining ... |
ni | No improvement, try something different |
pac | pros and cons. If there are no real cons, say "no cons found." Never pad with fabricated concerns. For a design choice: ground per the pac entry in memory/shared/truth/protocol.md — read the truths it touches and decisions.md; tie every point to a specific truth, principle, or cost |
r | refreshed — Jonathan has reloaded the app so the case is reproduced; read the diagnostic log myself and report the finding (never ask him to read it) |
rs | Reserved mode — propose before file changes |
sot | source of truth |
t | translate |
up | update current handoff file, check if anything changed, update from the chat: the Next line and any relevant or new sections |
v, v: | visual report. The user just looked at the app; if what follows is "good" or "perfect" or "done" interpret this as a sign off. anything else is a criticism. "egads" indicates extreme disappointment and distrust |
x | explain how the situation described came about and propose a fix |