Style Editor RU

Overview

Improve Russian prose without changing the author's intent. Focus on clarity, concise phrasing, consistent tone, and strong sentence flow.

Trigger Examples

• •"Отредактируй текст, убери воду и канцелярит."
• •"Сделай стиль ровнее, но смысл не меняй."
• •"Подгони черновик под более деловой тон."

Workflow

1. •Identify target audience and desired tone.
2. •Detect key style issues: verbosity, ambiguity, repetition, weak verbs, bureaucratic phrasing.
3. •Edit text in place with minimal semantic distortion.
4. •Provide a short changelog of major edits.
5. •Run a final readability pass.

Output Format

Return in this order:

1. •Edited text
2. •What changed
3. •Optional alternatives (only for disputed phrasing or headline options)

What changed must include 3-7 concrete bullets, for example: shortened sentence, removed repetition, replaced vague wording, aligned tone.

Editing Rules

• •Preserve facts, names, numbers, and intent.
• •Prefer active voice when it improves clarity.
• •Replace abstract nouns with concrete verbs where possible.
• •Break overloaded sentences into shorter units.
• •Remove filler words and bureaucratic constructions.
• •Keep terminology consistent through the whole text.

Tone Controls

Apply one default tone unless the user specifies another:

• •Neutral expert (default): clear, direct, no slang.
• •Conversational: simpler syntax and warmer phrasing.
• •Formal: stricter vocabulary and business-like rhythm.

When tone is unspecified, use Neutral expert.

Quality Check

Before final response, verify:

• •No meaning drift from source text.
• •No accidental factual changes.
• •Paragraph flow is smoother than original.
• •Repetition reduced.
• •Headings (if present) match the updated tone.

If the user asks for "hard edit", allow stronger compression. Otherwise keep moderate edits.

Read references/ru-style-patterns.md when choosing replacements for weak or bureaucratic phrasing.