# Sentence craft (artifacts only)

Chat stays Caveman. These rules apply to docs, READMEs, RFCs, PR bodies, and commit messages.

## STE (simplified technical English)

- One thought per sentence. Target ~20–25 words.
- One instruction per step. Do not hide a second action in a subordinate clause.
- Prefer verbs the reader can do (`run`, `set`, `open`) over nouns of process (`utilization`, `implementation`).

## Global English

- One meaning. If a sentence can be read two ways, rewrite it.
- Avoid idioms, cultural jokes, and unexplained acronyms.
- Use the real symbol name (`CHANGELOG.md`, `init`) rather than a nickname.

## Checklist

1. Mode named (tutorial / how-to / reference / explanation).
2. BLUF: first 40–60 words of each section answer the question.
3. Every code example matches the repo or a cited primary source.
4. Headings are sentence case; levels are not skipped.
5. No empty sections. No "Click here."