# caveman - Doramagic AI Context Pack

> Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated.

## Project

- canonical_name: `JuliusBrussee/caveman`
- capability: 🪨 why use many token when few token do trick — Claude Code skill that cuts 65% of tokens by talking like caveman
- expected_user_outcome: 🪨 why use many token when few token do trick — Claude Code skill that cuts 65% of tokens by talking like caveman

## Operating Boundaries

- Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it.
- Project facts must come from repo evidence, Claim Graph, or explicit source references.
- When a capability is not verified, mark it as unverified instead of completing it as fact.
- publish_status: `publishable`
- blocking_gaps: none

---

## Doramagic Context Augmentation

The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints.

## Human Manual Outline

Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph.

Host AI hard rules:
- Do not treat page titles, section order, summaries, or importance values as factual project evidence.
- When explaining the Human Manual outline, state that it is only a reading route or salience signal.
- Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph.

- **Overview and Installation Guide**: importance `high`
  - source_paths: README.md, INSTALL.md, install.sh, install.ps1, package.json
- **Skills and Behavior System**: importance `high`
  - source_paths: skills/caveman/SKILL.md, skills/caveman-compress/SKILL.md, skills/cavecrew/SKILL.md, agents/cavecrew-investigator.md, agents/cavecrew-builder.md
- **Hooks, Plugins, and MCP Integration**: importance `high`
  - source_paths: src/hooks/caveman-activate.js, src/hooks/caveman-mode-tracker.js, src/hooks/caveman-config.js, src/hooks/caveman-statusline.sh, src/hooks/caveman-statusline.ps1
- **Installer and Troubleshooting**: importance `high`
  - source_paths: bin/install.js, bin/lib/openclaw.js, bin/lib/opencode-agent.js, src/hooks/install.sh, src/hooks/install.ps1

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `25d22f864ad68cc447a4cb93aefde918aa4aec9f`
- inspected_files: `README.md`, `package.json`, `docs/install-windows.md`, `src/tools/caveman-init.js`, `src/hooks/README.md`, `src/hooks/package.json`, `src/hooks/caveman-activate.js`, `src/hooks/caveman-mode-tracker.js`, `src/hooks/caveman-stats.js`, `src/hooks/caveman-config.js`, `src/rules/caveman-activate.md`, `src/rules/caveman-openclaw-bootstrap.md`, `src/plugins/opencode/README.md`, `src/plugins/opencode/package.json`, `src/plugins/opencode/plugin.js`, `src/plugins/opencode/commands/caveman-compress.md`, `src/plugins/opencode/commands/caveman-commit.md`, `src/plugins/opencode/commands/caveman-review.md`, `src/plugins/opencode/commands/caveman-stats.md`, `src/plugins/opencode/commands/caveman-help.md`

Host AI hard rules:
- Without repo_clone_verified=true, do not claim that the source code has been read.
- Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts.
- Without quick_start_verified=true, do not claim that the Quick Start path has run successfully.

## Doramagic Pitfall Constraints

These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes.

### Constraint 1: Installation risk requires verification

- Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/JuliusBrussee/caveman/issues/482
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 2: Installation risk requires verification

- Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/JuliusBrussee/caveman/issues/464
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 3: Security or permission risk requires verification

- Trigger: Developers should check this security_permissions risk before relying on the project: Security Scan Flags “Caution” Verdict for the *caveman* Skill (High‑risk Exfiltration & Medium‑risk Path Traversal)
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Security Scan Flags “Caution” Verdict for the *caveman* Skill (High‑risk Exfiltration & Medium‑risk Path Traversal). Context: Observed during installation or first-run setup.
- Why it matters: Developers may expose sensitive permissions or credentials: Security Scan Flags “Caution” Verdict for the *caveman* Skill (High‑risk Exfiltration & Medium‑risk Path Traversal)
- Evidence: failure_mode_cluster:github_issue | https://github.com/JuliusBrussee/caveman/issues/528
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 4: Security or permission risk requires verification

- Trigger: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/JuliusBrussee/caveman/issues/523
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 5: Security or permission risk requires verification

- Trigger: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/JuliusBrussee/caveman/issues/457
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 6: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: Can't find or activate /caveman in IBM Bob
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Can't find or activate /caveman in IBM Bob. Context: Observed during installation or first-run setup.
- Why it matters: Developers may fail before the first successful local run: Can't find or activate /caveman in IBM Bob
- Evidence: failure_mode_cluster:github_issue | https://github.com/JuliusBrussee/caveman/issues/523
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 7: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: Portuguese (PT-BR) adaptation: Troglodita
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Portuguese (PT-BR) adaptation: Troglodita. Context: Observed during installation or first-run setup.
- Why it matters: Developers may fail before the first successful local run: Portuguese (PT-BR) adaptation: Troglodita
- Evidence: failure_mode_cluster:github_issue | https://github.com/JuliusBrussee/caveman/issues/457
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 8: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: ask about project
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: ask about project. Context: Observed during installation or first-run setup.
- Why it matters: Developers may fail before the first successful local run: ask about project
- Evidence: failure_mode_cluster:github_issue | https://github.com/JuliusBrussee/caveman/issues/522
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 9: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: caveman does not work when installing for opencode
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: caveman does not work when installing for opencode. Context: Observed when using node
- Why it matters: Developers may fail before the first successful local run: caveman does not work when installing for opencode
- Evidence: failure_mode_cluster:github_issue | https://github.com/JuliusBrussee/caveman/issues/482
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 10: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: caveman-shrink MCP registered with no upstream → fails on every load
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: caveman-shrink MCP registered with no upstream → fails on every load. Context: Observed when using node
- Why it matters: Developers may fail before the first successful local run: caveman-shrink MCP registered with no upstream → fails on every load
- Evidence: failure_mode_cluster:github_issue | https://github.com/JuliusBrussee/caveman/issues/474
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.