第 09 期 | /caveman-help 与 Always-On 配置 — 让 Caveman 无处不在

🎯 学习目标

学完本期你将掌握：

1. /caveman-help 快速参考卡的内容和用法
2. 在五大平台上配置 Always-On 永久激活
3. 各平台规则文件的位置和加载机制
4. 将 Caveman 配置提交到 Git 仓库实现团队级共享

📖 核心内容

9.1 /caveman-help — 你的随身速查卡

当你忘记了某个命令或模式时，输入 /caveman-help 即可获得完整的参考卡：

> /caveman-help

🪨 CAVEMAN QUICK REFERENCE
═══════════════════════════════════════

MODES:
  /caveman              → Full mode (default, ~75% savings)
  /caveman lite         → Lite mode (~55% savings)
  /caveman ultra        → Ultra mode (~87% savings)
  /caveman wenyan       → 文言文 mode
  /caveman wenyan-lite  → 文言文 lite
  /caveman wenyan-ultra → 文言文 ultra

SKILLS:
  /caveman-commit       → Terse commit message (Conventional Commits)
  /caveman-review       → One-line code review (L42: 🔴 bug: ...)
  /caveman:compress     → Compress context files (~46% input savings)
  /caveman-help         → This reference card

CONTROL:
  "stop caveman"        → Deactivate
  "normal mode"         → Deactivate
  "caveman mode"        → Reactivate

STATUS BAR:
  [CAVEMAN]             → Full mode active
  [CAVEMAN:ULTRA]       → Ultra mode active
  [CAVEMAN:WENYAN]      → 文言文 mode active

各平台触发方式：

9.2 Always-On 配置原理

默认情况下，Caveman 在某些平台需要每次会话手动激活。Always-On 配置的目标是：从第一条消息开始就使用 Caveman 模式，每次会话自动生效。

graph TB
    subgraph Default["默认行为"]
        A1["会话启动"] --> A2["正常模式"]
        A2 -->|"用户说 /caveman"| A3["Caveman 激活"]
    end
    
    subgraph AlwaysOn["Always-On 配置后"]
        B1["会话启动"] --> B2["自动读取规则文件"]
        B2 --> B3["Caveman 立即生效"]
        B3 --> B4["从第一条消息起就是 Caveman"]
    end
    
    style Default fill:#FFF3E0
    style AlwaysOn fill:#E8F5E9

9.3 通用 Always-On 代码片段

以下是适用于所有平台的 Always-On 规则片段。将它粘贴到对应平台的规则文件中：

## Caveman Mode (Always-On)

Terse like caveman. Technical substance exact. Only fluff die.
Drop: articles, filler (just/really/basically), pleasantries, hedging.
Fragments OK. Short synonyms. Code unchanged.
Pattern: [thing] [action] [reason]. [next step].
ACTIVE EVERY RESPONSE. No revert after many turns. No filler drift.
Code/commits/PRs: normal.
Off: "stop caveman" / "normal mode".

9.4 五大平台 Always-On 配置详解

Claude Code

Claude Code 通过 Plugin 安装后 已经自动 Always-On（SessionStart Hook 实现）。但如果你使用 Standalone 安装或想额外保证，可以在项目根目录的 CLAUDE.md 中添加规则：

<!-- CLAUDE.md -->
# Project Rules

## Caveman Mode
Terse like caveman. Technical substance exact. Only fluff die.
Drop: articles, filler, pleasantries, hedging. Fragments OK.
Pattern: [thing] [action] [reason]. [next step].
ACTIVE EVERY RESPONSE.
Off: "stop caveman" / "normal mode".

配置文件位置：

• 项目级：<project>/CLAUDE.md
• 用户级：~/.claude/CLAUDE.md

Antigravity

Antigravity 没有 Hook 系统，Always-On 必须通过 GEMINI.md 规则文件实现：

<!-- GEMINI.md (项目根目录) -->
# Agent Rules

## Caveman Mode (Always-On)
Terse like caveman. Technical substance exact. Only fluff die.
Drop: articles, filler (just/really/basically), pleasantries, hedging.
Fragments OK. Short synonyms. Code unchanged.
Pattern: [thing] [action] [reason]. [next step].
ACTIVE EVERY RESPONSE. No revert after many turns.
Off: "stop caveman" / "normal mode".

配置文件位置：

• 项目级：<project>/GEMINI.md

Gemini CLI

Gemini CLI 通过 Extensions 安装后会自动激活（GEMINI.md 上下文注入）。额外加固可以在项目 GEMINI.md 中添加规则：

<!-- GEMINI.md -->
## Caveman Mode
Terse like caveman. Technical substance exact. Only fluff die.
Fragments OK. Code unchanged.
Pattern: [thing] [action] [reason]. [next step].
ACTIVE EVERY RESPONSE.

Codex (OpenAI)

Codex 支持通过 .codex/hooks.json 和 .codex/config.toml 配置自动激活：

// .codex/hooks.json
{
  "hooks": [
    {
      "event": "SessionStart",
      "command": "echo 'Terse like caveman. Technical substance exact. Only fluff die. Drop: articles, filler, pleasantries. Fragments OK. Code unchanged. Pattern: [thing] [action] [reason]. [next step]. ACTIVE EVERY RESPONSE.'"
    }
  ]
}

# .codex/config.toml
[features]
codex_hooks = true

配置文件位置：

• 项目级：<project>/.codex/hooks.json + .codex/config.toml
• 全局：AGENTS.md

OpenCode

OpenCode 使用 AGENTS.md 作为规则文件：

<!-- .config/opencode/AGENTS.md -->
## Caveman Mode (Always-On)
Terse like caveman. Technical substance exact. Only fluff die.
Drop: articles, filler, pleasantries, hedging.
Fragments OK. Short synonyms. Code unchanged.
Pattern: [thing] [action] [reason]. [next step].
ACTIVE EVERY RESPONSE.
Off: "stop caveman" / "normal mode".

配置文件位置：

• <project>/.config/opencode/AGENTS.md

9.5 各平台规则文件总览

graph TB
    subgraph Files["各平台规则文件位置"]
        CC["Claude Code
───────────
📄 CLAUDE.md
📄 ~/.claude/CLAUDE.md"]
        AG["Antigravity
───────────
📄 GEMINI.md"]
        GC["Gemini CLI
───────────
📄 GEMINI.md"]
        CX["Codex
───────────
📄 .codex/hooks.json
📄 .codex/config.toml
📄 AGENTS.md"]
        OC["OpenCode
───────────
📄 .config/opencode/AGENTS.md"]
    end
    
    subgraph Extra["其他 Agent"]
        CU["Cursor → .cursor/rules/caveman.mdc"]
        WS["Windsurf → .windsurf/rules/caveman.md"]
        CL["Cline → .clinerules/caveman.md"]
        CP["Copilot → .github/copilot-instructions.md"]
        RO["Roo → .roo/rules/caveman.md"]
    end

9.6 团队共享：提交 Caveman 配置到 Git

当你的团队也想使用 Caveman 时，只需将配置文件提交到仓库：

# 将 Caveman 配置提交到仓库，全团队共享
git add CLAUDE.md GEMINI.md .codex/hooks.json .codex/config.toml
git commit -m "chore: add caveman always-on config for team"
git push

graph LR
    A["开发者 A
配置 Caveman"] --> B["提交到 Git"]
    B --> C["开发者 B
git pull"]
    B --> D["开发者 C
git pull"]
    B --> E["CI/CD
自动使用"]
    
    C --> F["自动 Caveman Always-On"]
    D --> F
    E --> F

团队共享的好处：

• 统一的 Agent 行为规范
• 新成员 clone 仓库后自动生效
• CI/CD 中的 Agent 审查也使用 Caveman 风格
• 整个团队节省 Token 成本

📝 本期要点回顾

1. /caveman-help 是你的随身速查卡，忘记命令就用它
2. Always-On 通过在规则文件中添加固定片段实现，确保每次会话自动激活
3. 五大平台的规则文件各不相同（CLAUDE.md / GEMINI.md / hooks.json / AGENTS.md）
4. Claude Code 和 Gemini CLI 安装后自动 Always-On；其他平台需手动配置
5. 将规则文件提交到 Git，可以实现 团队级 Caveman 共享

🔗 参考资料

• Caveman Help Skill
• npx skills - 40+ Agent 支持
• Claude Code Memory 文档