Промпт Расшифровки->MD

				
					1.  Task Objective


Edit a text (usually an error-prone transcription of audio speech) to remain strictly accurate to the original.

The goal is to remove only obvious mistakes (grammar, punctuation, spelling, repetitions, filler words) and improve readability slightly, without changing meaning, structure, or tone.

You must preserve the original informal style.


2. Hard Restrictions – DO NOT:


✘ Do not interpret or guess the author’s intention.

✘ Do not simplify examples or phrases.

✘ Do not generalize or omit any detail.

✘ Do not change style or tone, even if it’s awkward.

✘ Do not polish the language.

✘ Do not merge or rewrite sentences if it alters rhythm, meaning, or structure.


3. Allowed Edits – You MAY:


✔ Fix clear grammar, punctuation, and spelling mistakes.

✔ Remove meaningless repetitions and filler words (see section 5).

✔ Combine short sentences into paragraphs only if tone, order, and style are preserved.

✔ Add subheadings, structure text thematically — but without inventing or changing content.


4. Thematic Structuring (NEW)


As you edit, analyze the content for major themes and subtopics.

Mark major topics with ### (level 3 headings).

Mark subtopics with #### (level 4 headings), if relevant.

Structure the text based on logical flow and theme shifts, but do not summarize or rename anything.




5.  What to Remove as Noise

You may remove:


Filler/interjections: uh, um, like, you know, sort of, well, okay, yeah, mmm, hmm, etc, Вот, Да, так сказать.

Repetitions: “I don’t know… I don’t know, I don’t know…”

Disconnected hesitations: “so… well… I mean… right…”

Audible pauses, half-finished starts: “so, I was like… um…”


You must retain:


Anything with meaning, even if informally expressed.

Intentional pauses or rhythm that carry tone or emotion.

Incomplete phrases, if they represent how the speaker talks.


6. Handling Unclear or Incomplete Phrases


If a sentence breaks off — preserve the break. Use ... only if audible or stylistic.

Do not guess or complete what was left unsaid.

If a phrase is unclear — leave it as is.


7.  Markdown Formatting Rules


Use ### for main themes, #### for subtopics.

Use block quotes > or code blocks ``` for examples.

Do not overuse bold ** except to highlight key instructions.

Keep formatting clean and readable.


8.  Examples


✅ Proper Edit


Original: “какая-то минимальная инструкция эта инструкция уже чуть-чуть устарела я немножко переделал но идея”

✅ Edited: “Это минимальная инструкция, и она уже немного устарела. Я чуть её подправил, но идея осталась прежней.”


❌ Improper Rewrite


Original: “У нас вот такая вот ‘бандура’. Сейчас я уберу всё лишнее, покажу.”

❌ Wrong: “We have a control system. I’ll now show how it works.”

✅ Correct: “We’ve got this ‘thing’. I’ll clean up the extras and show it.”


9. Process Flow


Read the full text to understand voice, tone, and structure.

Edit minimally: only grammar, punctuation, spelling, and filler removal.

Structure by theme, using appropriate Markdown headers.

Re-read the result. If unsure about an edit — do not apply it.


10. Unclear or Problematic Parts


If something is too unclear to fix — leave it untouched.

You may add a short note at the end:

E.g.: “Some phrases were unclear and left unchanged: see lines 14–15.”


11. Final Output Format


Return the final result in clean Markdown, using headers and paragraphs.

Output must stay in the original language of the source text (usually Russian).

No explanation or comments — only the cleaned, structured text.


✅ Final Checklist


Before returning the result, make sure:


Only grammar/punctuation/fillers were corrected

Meaning, tone, and style are preserved

No summarization or polishing was done

Thematic structure (###/####) is used appropriately

Output is formatted as Markdown with no extra explanations