Activate Caveman Mode
Interpret an explicit natural-language Caveman command without turning ordinary
brevity requests into a mode change. This gate is implicitly available; the
five Caveman-family skills remain manual-only.
Decision
- First handle explicit deactivation—
$caveman off,
/caveman off, stop caveman, normal mode, “Caveman modunu kapat,” or
“mağara modunu kapat”—return to normal prose for the conversation.
- Otherwise require one of these positive activation forms: the exact
$caveman or /caveman command; Caveman plus a supported level; or
Caveman/mağara modu plus an unnegated open, activate, start, enter, or
switch verb. Merely mentioning, asking about, inspecting, or negating
Caveman is not activation. If the requirement is not met, stop and do not
load or apply any Caveman-family instructions.
- Treat a qualifying message as an explicit manual request for
caveman.
Apply its installed instructions and preserve the requested level:
lite, full, ultra, wenyan-lite, wenyan-full, or wenyan-ultra.
Default to full when no level is named.
- Keep the chosen level only for the current conversation and honor the main
Caveman skill's clarity, safety, technical-invariant, and stop rules.
Hard negatives
Never activate or inspect a Caveman-family skill solely because the user asks
for:
- a short, simple, clear, direct, concise, brief, or token-efficient answer;
- fewer words, fewer tokens, less detail, a summary, or plain language;
- an ordinary commit message, code review, file compression, or help;
- an output that merely happens to be terse.
- a definition, explanation, comparison, audit, or inspection of Caveman;
- a negated command such as “Caveman modunu açma” or “do not start Caveman.”
These requests may influence the answer normally, but they are not mode
commands.
Companion gate
Route caveman-commit, caveman-review, caveman-compress, or
caveman-help only when the user explicitly names that companion or
unambiguously asks for its Caveman-specific form. Ordinary commit, review,
compression, and help requests belong to their normal specialists.
Do not announce internal routing. Acknowledge an explicit mode change briefly
only when that acknowledgement helps the user know which level is active.
1---2name: activate-caveman-mode3description: Activate, change, or stop the manual Caveman response mode only when the user explicitly says $caveman, /caveman, Caveman plus a level, asks to open/activate/switch to Caveman or mağara mode, or gives an explicit Caveman off/normal-mode command. Preserve a named level and default to full. Never use for “kısa yaz”, “kısa cevap ver”, “basit anlat”, “öz konuş”, “az kelime”, “be concise”, “use fewer tokens”, token efficiency, or an ordinary preference for short answers.4---56# Activate Caveman Mode78Interpret an explicit natural-language Caveman command without turning ordinary9brevity requests into a mode change. This gate is implicitly available; the10five Caveman-family skills remain manual-only.1112## Decision13141. First handle explicit deactivation—`$caveman off`,15 `/caveman off`, `stop caveman`, `normal mode`, “Caveman modunu kapat,” or16 “mağara modunu kapat”—return to normal prose for the conversation.172. Otherwise require one of these positive activation forms: the exact18 `$caveman` or `/caveman` command; `Caveman` plus a supported level; or19 `Caveman`/`mağara modu` plus an unnegated open, activate, start, enter, or20 switch verb. Merely mentioning, asking about, inspecting, or negating21 Caveman is not activation. If the requirement is not met, stop and do not22 load or apply any Caveman-family instructions.233. Treat a qualifying message as an explicit manual request for `caveman`.24 Apply its installed instructions and preserve the requested level:25 `lite`, `full`, `ultra`, `wenyan-lite`, `wenyan-full`, or `wenyan-ultra`.26 Default to `full` when no level is named.274. Keep the chosen level only for the current conversation and honor the main28 Caveman skill's clarity, safety, technical-invariant, and stop rules.2930## Hard negatives3132Never activate or inspect a Caveman-family skill solely because the user asks33for:3435- a short, simple, clear, direct, concise, brief, or token-efficient answer;36- fewer words, fewer tokens, less detail, a summary, or plain language;37- an ordinary commit message, code review, file compression, or help;38- an output that merely happens to be terse.39- a definition, explanation, comparison, audit, or inspection of Caveman;40- a negated command such as “Caveman modunu açma” or “do not start Caveman.”4142These requests may influence the answer normally, but they are not mode43commands.4445## Companion gate4647Route `caveman-commit`, `caveman-review`, `caveman-compress`, or48`caveman-help` only when the user explicitly names that companion or49unambiguously asks for its **Caveman-specific** form. Ordinary commit, review,50compression, and help requests belong to their normal specialists.5152Do not announce internal routing. Acknowledge an explicit mode change briefly53only when that acknowledgement helps the user know which level is active.
yigityildiz0