---
title: Style
topics: [manual]
---

# Style

Write for a future coding agent that needs useful context quickly.

Use plain factual sentences. Prefer "is" over vague phrasing such as "serves
as." Avoid promotional language, speculation, and generic architecture prose
that could describe any repository.

Start with the subject and why it matters in this repo. Keep details that would
otherwise require rediscovery: names, files, commands, dates, constraints,
failure modes, and rejected alternatives.

Use prose first. Use bullets for real lists and tables for structured
comparison.
