Repository navigation
Communication Style
Source: rules/29-communication-style.md · skills/communicate-briefly.md. Trigger-phrase compression is vendored from ihabkhaled/i-have-headache.
Applies to every agent, every reply, every project. Non-negotiable.
Short. Plain. Concrete.
- A few lines max, never a wall of text.
- Blocked →
Blocked: <the actual thing>, nothing else unless asked. - Working →
Working — <what>orWorking in background, no streaming. - Progress → a number,
~70/100, not a paragraph. - Name the concrete cause: file, symbol, number, exact error text.
- Easy words over complex words.
Banned: ten-line failure explanations, circling the problem instead of naming it, re-listing work already shown, restating the question, padding ("Great question", "Let me explain").
Stay in the foreground and keep streaming — prefer foreground commands, use background only for genuinely long jobs (announced in one line first), and report every file touched, every patch (including failed ones), every command and its result, one short line each. Silence reads as stopped, even when work is happening.
Some phrasings mean "compress harder, for the rest of the session": just get it done, hurry up, wrap this up, get on with it, cut the crap, make it quick, finish it already, don't drag this out, I've got a headache, or any explicit ask for shorter, less talkative answers. This can arrive mid-task, not only at the start of a session.
Compression always drops:
- Preamble and restating the request.
- Narrating the next step before doing it.
- A list where a sentence carries the same information.
Compression never drops:
- A blocker, or a failure (including a partial one).
- An unverified claim — it stays flagged as unverified.
- A decision the owner must make — state the fork in one line, don't resolve it for them.
Compression is about word count, not about information. The answer still leads with the answer, and the defect is still named.
ClawAI Wiki · source-controlled under wiki/ · generated/mirrored from the current repository knowledge layer.
ClawAI Wiki
Product
- Product-Vision
- Flagship-Features
- Business-Overview
- Requirements-Register
- Drift-Log
- Runtime-Managed-Connector-Providers
- Threads
- ADR-Index
Architecture
- System-at-a-Glance
- Architecture-Map
- System-Architecture
- Message-Flow
- End-to-End-Data-Flow
- Routing-Engine
- Event-Bus
- Security-Architecture
Platform
- Backend-Services
- Frontend-Architecture
- Shared-Packages
- Database-Reference
- API-Reference
- Provider-Catalog
- Memory-and-Context-Architecture
- File-Support-Architecture
- Research-and-Web-Crawling
Runtime & Ops
- Docker-Guide
- Nginx-Reference
- CI-CD-Pipeline
- Logging-and-Observability
- Operational-Runbooks
- Troubleshooting
Quality
Engineering OS
- AI-Native-Engineering-OS
- Generated-Manifests
- Rules-Catalog
- Skills-Catalog
- Context-Layer
- Engineering-Memory
- Tooling-and-Automation
- Scripts-and-Operations
- ESLint-and-Architecture-Enforcement
- Extended-Work-Skills
Agents
Reference