Shorthand

Short commands and abbreviations for working with collaborator. NB: ALL urls on this page are relative to ~/GitHub/mono/

Command	Action
help	Show this table
claude	Reread <current-go>/CLAUDE.MD
egads	Jonathan is extremely disappointed and has far less trust that you and he can succeed
memory	Describe any useful auto-generated insights from userMemories (normally ignored)
tokens	crude (rough, loose) estimated percentage of context consumed (okay with me that no exact measurement is available, just give me a number)
proposal	describe your plan before executing
undo, revert	Revert last file change
chime	In plain english, very briefly give observations, suggestions, corrections about the topic at hand
learn, decision	Summarize the mistake you just made, add it to learn, and report number of pending entries
shorthand	Read this file (shorthand.md)
translate, rewrite	Rewrite the last response using concise, plain english. Avoid jargon.
geometric	use names of SO rather than obj_N, use label names of eps when describing faces, segs or eps
update, done	simplify code debt by moving checked off things to code debt paid. simplify and tighten handoff, moving done things to work journal. update work journal, working features, map and file layout
setup	for the current project, create whatever notes/work/now/ files are missing per the minimal set in notes/guides/collaborate/workflow.md: code.debt.md always; handoff.md and the rest only when asked. never overwrite an existing file; report what got created
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
mothball	state and confirm the context. then gather everything relevant into a mothball file
gobbledegook, mess, verbose	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

Abbreviations

Abbreviation	Meaning
ex	Execute mode — skip proposals, just do it
rs	Reserved mode — propose before file changes
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.
cd	read code.debt.md
up	update current handoff file, check if anything changed, update from the chat: the Next line and any relevant or new sections
dev	read all md files in notes/guides/develop (in both mono and <current-go>)
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