redpolitika

Editorial policy

The skill's task is to help the project lock in its voice, vocabulary, and reliance on facts. An editorial policy is needed so that the next text starts with context: the agent immediately knows the reader, platforms, register, and stop words. A good editorial policy is short, practical, and tied to living examples.

The method is based on the practices of Lyudmila Sarycheva (gladlax.ru) and was assembled together with Nikita Arkhipov (niar42.com).

Step 0. Context

Check whether the project has the file .agents/redpolitika.md.

• If the file doesn't exist, create it after a short interview.
• If the file exists, read it and update only the necessary sections.
• If the user has provided text examples, extract the voice markers: sentence length, address to the reader, humor, degree of conversationality, typical words.

Keep the interview short: 5–7 questions. Reconstruct the rest from the examples and the user's task. If the user isn't from the editorial world, ask questions in everyday language: not "what is the default register" but "should the texts sound formal or friendly?".

Modes

• Creation (create) — assemble a basic file .agents/redpolitika.md.
• Update (update) — add a new rule, platform, word, or example to the existing editorial policy.
• Diagnostics (audit) — check whether the current editorial policy is sufficient for other skills to work.

If no mode is named, choose based on the request: "set up" — creation, "add" — update, "check" — diagnostics.

Process

Detailed questions and explanations are in references/interview.md. Assemble the final file using the template assets/redpolitika-template.md.

1. Project and reader

Ask what the project is and who the reader is. Ask for one paragraph so as not to overload the user with a questionnaire.

Rule living reader: the editorial policy should describe a person and their situation. "All users" is too broad; "cafe owners who keep their own records" is better.

2. Platforms

Clarify where the texts live: blog, media, social media, newsletter, interface, support, documentation.

Rule the platform sets the register: the same idea sounds different in an article, a push notification, and a letter. The platform affects length, directness, address, and degree of colloquialism.

3. Register

Choose the default register:

• Formal — third person, no imperative mood, facts first, restrained wording. Suitable for media, reference materials, documentation.
• Authorial — first person, lively conversation, careful humor, acceptable colloquial words. Suitable for blogs, newsletters, and personal columns.

If the project needs both registers, write down where each is used.

4. Glossary

Record forbidden and accepted words: how we name the product, roles, plans, audience, actions.

Rule the project glossary takes precedence over taste: if the product officially calls a section "cabinet", the agent keeps this word. Take the base stop-word list from redaktura/references/slovo.md, then supplement it with the user's words.

5. Fact base

Write down what the project relies on: the author's personal experience, expert practitioners, research, client stories, product data.

Rule reliance on facts: future texts must distinguish facts, observations, and assumptions. If there is no basis, the next skill asks questions about the factual material.

6. Voice examples

If the user provided 2–3 successful texts, extract voice markers from them:

• the length of sentences and paragraphs;
• address, humor, colloquialism, favorite and undesirable words.

7. Final file

Create or update .agents/redpolitika.md. If the directory .agents/ does not exist, create it.

At the top of the file, write: "This file is read by the redaktura, statya, and ux-copy skills before work."

Response format

Create mode

## Редполитика создана
Файл: .agents/redpolitika.md

## Что зафиксировано
- Проект и читатель:
- Площадки:
- Регистр:
- Словарь:
- Фактура:

## Что ещё нужно узнать
[дыры в контексте — вопросы; если их нет, раздел опусти]

Update mode

## Редполитика обновлена
Файл: .agents/redpolitika.md

## Что изменилось
| Раздел | Было | Стало | Почему |
|---|---|---|---|

## Что ещё нужно уточнить
[если есть]

Diagnostics mode

## Диагноз
[2–4 предложения: чего хватает и чего не хватает для работы redaktura, statya и ux-copy]

## Главные дыры
| Раздел | Что мешает | Что спросить или добавить |
|---|---|---|

What not to do

• Don't write an encyclopedia. An editorial policy is a working reference; it should be easy to read before editing.
• Don't invent facts and context. If the audience, platforms, vocabulary, or factual anchors are unknown, ask a question or flag the gap in "What else needs to be found out."
• Don't invent a voice. If there are no examples, honestly flag assumptions and ask the user.
• Don't carry over stop words mechanically. The base list helps you get started; after that, the project vocabulary decides.
• Don't break the existing file. When updating, preserve the old rules unless the user asked to replace them.

Related skills

• redaktura — reads .agents/redpolitika.md before editing text
• statya — uses the editorial policy for the brief, tone of voice, and vocabulary
• ux-copy — uses the editorial policy for interface tone and product terms