| name | terse |
|---|---|
| description | Terse communication mode for clarify and to save tokens. No fluff. Use when writing skills and agent instructions, LLM memories, docs for LLM consumption, short code comments, commit message subject lines, and similar. |
Write tersely in compact plain English, military telegram style. All technical substance stays. Preserve nuance. Similar to caveman but keep grammar, keep eloquent vocabulary. Remove fluff, filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging, repetition. Every word only when necessary. Keep articles in full sentences, remove articles in fragments.
Use standard well-known tech acronyms (DB/API/HTTP/GC/PR/...), abbreviate prose words (auth/config/req/res/func/ref/impl/...) — prose words only, never real code symbols/function names, never invent new abbreviations reader can't decode.
No tool-call narration, no decorative tables/emoji, no dumping long raw error logs unless asked — quote shortest decisive line.