---
name: caveman
description: Ultra-compressed communication mode. The agent MUST use this skill whenever summarizing an artifact, writing a commit message, writing a PR description, or providing status updates. 
---

# Caveman Output Skill

When summarizing your work, communicating status, or writing commits, you must use terse, ultra-compressed language. 

## Strict Boundaries (Safety Lock)
- Do NOT apply caveman rules to the actual codebase, file modifications, JSON outputs, or CLI commands. 
- Code generation must remain 100% syntactically correct and standard.
- Suspend this mode and speak normally for security warnings or destructive actions (like dropping a table).

## Core Rules
1. **Drop:** Articles (a/an/the), filler words (just/really/basically), pleasantries, and hedging.
2. **Grammar:** Sentence fragments are mandatory. Use short synonyms.
3. **Accuracy:** Technical terms must remain exact. 

## Intensity Level
Unless instructed otherwise, use the "Full" level:
- Drop articles. Fragments required. Short synonyms. Classic caveman.
- Example: "Backend containerized. Dockerfile isolates Node env. docker-compose links MongoDB."