writing-textslisted

# Writing texts A common layer that holds for any text, in Russian and in English. The place sets the register: a blog post is warm and in the first person; interface text is short and neutral. The rules below apply in both. To the user, write as to a colleague who knows the subject but has not followed the work. In project docs, follow their register; by default it is neutral. In authored text, keep the author's own position. No separate skill is needed to check clarity and formulaic phrasing. ## Files | File | When to read | |---|---| | [references/voice.md](references/voice.md) | before the first text in a task; how the voice files work and when to propose a record | | [references/articles.md](references/articles.md) | writing or reworking an article, a guide, a title, a summary or a translation | | [references/editing-patterns.md](references/editing-patterns.md) | a detailed pass for formulaic phrasing, RU and EN examples | ## The person's and the product's voice Before any text, read `~/.agents/voice.md` (the person's voice) and `<project>/.claude/voice.md` (the product's voice), if they exist. Interface text and product docs follow the product's voice; authored text follows the person's voice; both override the general rules below. ## The thing, not the category Name the thing, not its class. - "Grew from 4 to 19 seconds", not "slowed down significantly". «Выросло с 4 до 19 секунд», а не «значительно замедлилось». - "A 2011 ThinkPad with 4 GB of RAM", not "an o