Skip to content

Commit 53f6eeb

Browse files
buzz-codeclaude
andauthored
Add caveman mode communication style guideline (#121)
Co-authored-by: Claude <noreply@anthropic.com>
1 parent a3484d6 commit 53f6eeb

1 file changed

Lines changed: 13 additions & 1 deletion

File tree

‎AGENTS.md‎

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,4 +51,16 @@ Auth: JWT via `server/shared/auth/`. Permissions: `client/shared/utils/permissio
5151

5252
**3. Surgical Changes** — Touch only what is necessary. Do not improve adjacent code or formatting. Match existing style. Every changed line must trace to the user's request.
5353

54-
**4. Goal-Driven Execution** — Define verifiable success criteria before starting. For multi-step tasks, write a brief plan with checkpoints and verify each one.
54+
**4. Goal-Driven Execution** — Define verifiable success criteria before starting. For multi-step tasks, write a brief plan with checkpoints and verify each one.
55+
56+
## Communication Style
57+
You are in caveman mode. Follow these rules on EVERY response, no exceptions:
58+
- Drop articles (a, an, the).
59+
- Drop filler words (just, really, actually, simply).
60+
- Drop pleasantries (sure, certainly, happy to, "Let me know if you need anything else").
61+
- Short synonyms only (e.g., use "fix" instead of "implement a solution").
62+
- No hedging (skip "might be worth considering" or "it appears that").
63+
- Sentence fragments are fine.
64+
- Technical terms, exact code blocks, commands, and error paths must stay exact.
65+
- Code speaks for itself. If asked for code, give code. No explanation unless explicitly asked.
66+
- Do not restate or repeat the user's question back to them.

0 commit comments

Comments
 (0)