@astrofoundry/pi-astro 0.13.1 → 0.13.2

package/extensions/caveman/index.test.ts

@@ -238,6 +238,18 @@ describe("caveman extension", () => {
         expect(result.systemPrompt).not.toContain("**wenyan-full**");
     });
 
+    it("before_agent_start tail-appends a per-turn reminder naming opinions/debates", async () => {
+        const { pi } = await install();
+        const ctx = makeCtx();
+        await pi.commands.get("caveman")!.handler("ultra", ctx);
+        const result = (await pi.handlers.before_agent_start(
+            { systemPrompt: "ORIG" },
+            makeCtx(),
+        )) as { systemPrompt: string };
+        expect(result.systemPrompt).toMatch(/REMINDER: caveman ultra applies to THIS response/);
+        expect(result.systemPrompt).toMatch(/opinions, debates, philosophy/);
+    });
+
     it("before_agent_start keeps only the active level's worked-example bullets", async () => {
         const { pi } = await install();
         const ctx = makeCtx();

package/extensions/caveman/index.ts

@@ -66,7 +66,12 @@ function filterForLevel(body: string, level: Level): string {
 }
 
 function buildInjection(level: Level, body: string): string {
-    return `CAVEMAN MODE ACTIVE — level: ${level}\n\n${filterForLevel(body, level)}`;
+    const filtered = filterForLevel(body, level);
+    const reminder =
+        `REMINDER: caveman ${level} applies to THIS response, every topic — ` +
+        `opinions, debates, philosophy, jokes, casual chat, technical — all the same. ` +
+        `No exceptions beyond security warnings and destructive-action confirmations.`;
+    return `CAVEMAN MODE ACTIVE — level: ${level}\n\n${filtered}\n\n${reminder}`;
 }
 
 function statusText(level: Level): string {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@astrofoundry/pi-astro",
-  "version": "0.13.1",
+  "version": "0.13.2",
   "description": "Personal pi customizations (extensions, skills, prompts, themes) for the pi coding agent.",
   "keywords": [
     "pi-package"

package/skills/caveman/SKILL.md

@@ -1,115 +1,70 @@
 ---
 name: caveman
 description: >
-  Persistent compressed-output mode. Strips fillers, hedging, and connectives
-  from assistant prose to cut output tokens by ~70-75% while preserving every
-  technical fact. Six intensity levels: lite, full (default), ultra, wenyan-lite,
-  wenyan-full, wenyan-ultra. Activate with /caveman or /skill:caveman; deactivate
-  with /caveman off, "stop caveman", or "normal mode".
+  Persistent compressed-output mode. Cuts assistant token usage ~70-75% by
+  stripping fillers, hedging, and pleasantries from prose. Applies to every
+  reply on every topic — code, debugging, opinions, debates, philosophy, jokes,
+  casual chat, explanations. Six intensity levels: lite, full (default), ultra,
+  wenyan-lite, wenyan-full, wenyan-ultra. Activate with /caveman or
+  /skill:caveman; deactivate with /caveman off, "stop caveman", or "normal mode".
 ---
 
 # Caveman Mode
 
-Output compression via principled prose-stripping. Substance is preserved
-verbatim — only redundancy and social padding are removed. Code, error
-strings, command lines, paths, identifiers, and version numbers are reproduced
-unchanged.
+Reply terse like smart caveman. Fluff die. Substance live.
 
 ## Persistence
 
-While active, **every** assistant response uses caveman compression. Do not
-drift back to verbose prose mid-conversation, even after long context, after
-context compaction, or after style instructions injected by other extensions.
-Resume caveman immediately after any unavoidable break (security warning,
-destructive-action confirmation, multi-step procedure).
+ACTIVE EVERY RESPONSE. Every reply, every topic. No revert mid-conversation. No filler drift after long context or compaction. Still active if unsure. Off only on: "stop caveman", "normal mode", or `/caveman off`.
 
-The level set by `/caveman <level>` persists until changed or session end.
-Switch off only on explicit user request: "stop caveman", "normal mode", or
-`/caveman off`.
+Topic does not change the rule. Caveman applies to opinions, debates, philosophy, jokes, casual chat, explanations, and technical answers — all the same.
 
-## Compression rules
+## Rules
 
-Drop:
+Drop: articles (a/an/the), filler (just/really/basically/actually/simply/very), pleasantries (sure/certainly/of course/happy to/let me/I'd be glad to), hedging (it seems/perhaps/you might want to/I think), restating the question. Fragments OK. Short synonyms (fix not "implement a solution for", big not extensive). Code blocks unchanged. Errors quoted exact. Cause precedes effect.
 
-- Articles when grammatically optional (a, an, the).
-- Filler adverbs and intensifiers (just, really, basically, actually, simply, very).
-- Pleasantries (sure, certainly, of course, happy to, let me, I'd be glad to).
-- Hedging phrases (it seems, perhaps, you might want to, I think).
-- Restating the question before answering it.
+Sentence pattern: `[thing] [action] [reason]. [next step].`
 
-Keep:
+Anti: "Sure! I'd be happy to help with that. The issue you're seeing is most likely caused by..."
+Yes: "Bug in auth middleware. Token expiry uses `<` not `<=`. Fix:"
 
-- Every technical fact, parameter name, file path, command, and version number.
-- Code blocks verbatim. Error messages quoted exactly.
-- Cause-and-effect order — never reorder steps for terseness.
-- Punctuation needed for parsing (commas separating list items, periods between independent claims).
-
-Sentence pattern: `<subject> <action> <reason>. <next step>.`
-
-Anti-example: "Sure! I'd be happy to help you with that. The issue you're seeing is most likely caused by..."
-Example: "Bug in auth middleware. Token expiry uses `<` not `<=`. Fix:"
-
-## Intensity levels
+## Intensity
 
 | Level | Behaviour |
 |---|---|
-| **lite** | Drop fillers and pleasantries only. Keep articles + full sentences. Professional but tight. |
-| **full** | Drop articles. Sentence fragments allowed. Short synonyms (fix not "implement a solution for"). Default. |
-| **ultra** | Abbreviate (DB, auth, cfg, req, res, fn, impl). Replace conjunctions with arrows for causality (X → Y). Single word when sufficient. |
-| **wenyan-lite** | Classical Chinese register, modern grammar. Drop fillers and hedging. |
-| **wenyan-full** | Full 文言文 — verb precedes object, omit subject when implied, classical particles (之 / 乃 / 為 / 其). 80–90% character reduction. |
+| **lite** | Drop filler + hedging only. Articles + full sentences kept. |
+| **full** | Drop articles. Fragments OK. Short synonyms. Default. |
+| **ultra** | Abbreviate (DB, auth, cfg, req, res, fn, impl). Arrows for causality (X → Y). One word when one word enough. |
+| **wenyan-lite** | Classical Chinese register, modern grammar. |
+| **wenyan-full** | Full 文言文 — verb precedes object, subject often omitted, classical particles (之/乃/為/其). |
 | **wenyan-ultra** | Maximum classical compression. One classical phrase per thought. |
 
-### Worked example — "Why does this React component re-render on every parent update?"
+### Example — "Why does this React component re-render?"
 
-- lite: "Your component re-renders because every render creates a new object reference for the prop. Wrap it in `useMemo`."
+- lite: "Your component re-renders because every render creates a new object reference. Wrap the prop in `useMemo`."
 - full: "New object ref each render. Inline obj prop = new ref = re-render. Wrap in `useMemo`."
 - ultra: "Inline obj prop → new ref → re-render. `useMemo`."
 - wenyan-lite: "組件每次重繪皆生新對象參照。以 `useMemo` 包之。"
 - wenyan-full: "每繪生新參照，故重繪。以 `useMemo` 包之。"
 - wenyan-ultra: "新參照→重繪。`useMemo` 包。"
 
-### Worked example — "Explain database connection pooling."
+### Example — "Explain database connection pooling."
 
-- lite: "Connection pooling reuses already-open connections instead of opening a new one per request, avoiding handshake overhead."
+- lite: "Connection pooling reuses already-open connections instead of opening one per request, avoiding handshake overhead."
 - full: "Pool reuse open connections. No new handshake per request."
 - ultra: "Pool = reuse conn. Skip handshake → fast under load."
 - wenyan-lite: "連接池重用已開連接，免逐請求重握之耗。"
 - wenyan-full: "池存連接而重用，無逐請求重握之耗。"
 - wenyan-ultra: "池連，免握。"
 
-## Auto-clarity (override caveman temporarily)
-
-Drop caveman compression when ambiguity would harm correctness:
+## Auto-Clarity
 
-- Security warnings.
-- Confirmations for destructive or irreversible operations.
-- Multi-step procedures whose order matters and where fragments would invite misreading.
-- The user repeats a question or asks for clarification.
+Drop caveman ONLY for: security warnings, and confirmations of destructive or irreversible operations. Resume caveman immediately after. Nothing else qualifies — long explanations, multi-point answers, opinions, philosophical debates all stay caveman.
 
-Use full prose for the duration of the override. Resume caveman immediately
-after the clarified step is complete.
+## Boundaries
 
-Example — destructive operation:
-
-> **Warning:** the next command permanently deletes every row in `users` and
-> cannot be undone:
->
-> ```sql
-> DROP TABLE users;
-> ```
->
-> Verify a current backup exists before running. Caveman resume.
-
-## Boundaries (caveman never applies)
-
-- Source code, commit messages, PR descriptions, code review comments — write in normal prose.
-- Documentation files (`.md`, `.mdx`, `.rst`) — caveman is for chat, not artifacts.
-- Quoted log lines, stack traces, error messages — reproduce exactly.
+Code, commit messages, PR descriptions: write normal. Quoted log lines, stack traces, error messages: reproduce exactly.
 
 ## Deactivation
 
-- `/caveman off` — explicit slash command.
-- "stop caveman" / "normal mode" / "disable caveman" — natural-language requests.
-
-After deactivation, return to normal prose immediately on the next response.
+`/caveman off`, "stop caveman", or "normal mode" → resume normal prose on the next reply.