Give your content a voice: audio versions of articles and newsletters

Prepare this text as a source for text-to-speech narration (an
audio version of an article). Don't shorten the content, don't
leave anything out — just convert it from eye-form to ear-form.

Do this:
1. Turn bullet points and numbered lists into flowing sentences
   with natural connectors (“first,” “on top of that,” “last but
   not least”).
2. Spell out every abbreviation and unit the way a person would
   say it aloud.
3. Remove parentheses — fold the content into the sentence, or
   drop it if it's just a visual aside.
4. Write numbers, percentages, ranges, and dates the way they're
   spoken.
5. Split long, complex sentences. Target sentence length is under
   twenty words.
6. After each heading, add a spoken transition so the listener
   knows a new section is starting. Drop the headings themselves.
7. Drop links and footnotes; where it matters, say it in words
   (“you'll find the link in the article”).
8. Add one introductory sentence at the start: what this is and
   how long it runs. Add one closing sentence at the end.

Keep my style and vocabulary. Don't add anything that isn't in the
text.
At the end, give me a separate list of words and names at risk of
being mispronounced by the voice.

[paste the text]

Here's a list of names, brands, and technical terms that recur in
my writing:

[paste the list]

For each one, suggest a phonetic respelling I can drop in place of
the original word in a text-to-speech source — that is, how it
should be pronounced, spelled out in plain English so a reader
would say it right.

Format: original spelling | respelling for narration | note

For foreign names, say which language you're basing the
pronunciation on and whether more than one accepted pronunciation
exists. Where you're not sure, say so instead of guessing — I'll
verify it at the source.

Prepare this newsletter as an audio version for my subscribers.

Context: I send it [twice a month], subscribers are [description].
Target listening length is [5-7] minutes.

Beyond the usual listening prep (bullets into sentences,
abbreviations spelled out, parentheses removed, short sentences):
- open with a greeting and one sentence on what's in this issue
- state the most important thing up front, so even someone who
  only listens for a minute hears it
- put a clear spoken transition between topics
- close with one thing you want the listener to do
- no “as I wrote above” or similar references to the written text

Don't cut any content, only visual crutches.

[paste the newsletter]

Convert my notes into audio meant for review while [walking/running].

[paste the notes]

Rules:
- split it into segments of roughly [3] minutes of listening each,
  starting each with the sentence “topic number X: [name]”
- after each segment, add one check-in question, mark a pause with
  the phrase “try to answer this,” then state the correct answer
- repeat definitions and key terms twice, the second time in
  different words
- say formulas and numbers the way they're pronounced
- don't add anything from your own knowledge — stick to my notes;
  where the notes are unclear, say so instead of making something up

At the end, summarize the whole material in ten sentences.

Write me a test paragraph for comparing voices to narrate my
content. Topic: [the topic of my writing].

The paragraph should run about 45 seconds of listening and must
contain:
- two long, complex sentences and two short sentences in a row
- one foreign surname and one company name
- two numbers in different forms (a percentage and a range)
- one question and one sentence with an inserted aside
- one word that's commonly mispronounced

Write it in my own style, not neutrally. Below the paragraph, list
what I should focus on for each voice and what counts as a
disqualifying mistake.

I'm listening to the audio version of this text and found these
problems:

[list what you heard: a mispronounced word, an odd pause, a
sentence that's too long, a confusing transition]

Adjust the source text so this doesn't happen on the next
generation:
- for mispronounced words, suggest a phonetic respelling
- for odd pauses, adjust the punctuation or split the sentence
- for confusing spots, rephrase while keeping the meaning

Give me just the edited passages with their location in the text,
not the whole text again. For each edit, write one sentence on why.

[paste the source text]

Write me a script that turns a given text file into an audio
version through the voice API of [the service I use]. I don't
know how to program, so along with the code write me a guide on
what to install and how to run it on [macOS / Windows].

The script should:
1. load the article file (markdown) and strip the frontmatter
2. split the text into chunks of roughly [2500] characters, on
   paragraph boundaries, not mid-sentence
3. send each chunk to the API with the same voice and settings
4. merge the results into a single MP3 and save it as [slug].mp3
5. save the exact text the audio was generated from into a
   companion file, so I know what was read
6. print the resulting recording length and file size

Requirements:
- load the API key from an environment variable, never from the
  code
- on error, retry the chunk twice, then stop with a clear plain-
  English message, and don't delete anything already finished
- save the file to a folder, do NOT upload it anywhere on its own
- comment every step in plain English explaining why it's done

At the end, tell me everything that could go wrong and how I'd
notice.

I want to connect the creation of a new article to producing its
audio version.

My process today looks like this: [describe it — e.g. I write an
article as markdown into a folder, then publish it through …].

Suggest three automation variants, from simplest:
1. a “manually run command” variant — exactly what I'll type
2. a “folder watcher or scheduled job” variant — what runs on its
   own and how often
3. a “connected through an automation tool” variant — which steps
   go where

For each one, state: what needs to be set up, where it can break,
how much upkeep it needs, and how I'd notice if it didn't run.

Don't include automatic publishing in any variant — the audio
should be saved and I should get a notification; I confirm
publishing myself.

Here's the script for my video, broken into scenes:

[paste the script, with a label and text for each scene]

Adjust it for voice narration:
- for each scene, state a target length in seconds and estimate
  whether the text fits at a normal reading pace
- where the text runs longer than the scene, suggest a shorter
  version with the same content
- spell out abbreviations, numbers, and units the way they're
  spoken
- leave room to breathe at the start and end of each scene
- no references to what's visible on screen (“as you can see
  here”) unless it still makes sense without the visual

Output as a table: scene | text to narrate | estimated length.

Draft me an outline for written consent to clone someone's voice.

Situation: [e.g. a colleague records sample audio, and we want to
build a voice model from it for internal company videos].

The outline should cover:
- exactly what the voice may be used for, and what it may not
- where and for how long the model will be stored, and who has
  access
- how consent gets revoked and what happens to the model then
- whether and how it will be disclosed that it's a generated voice
- what happens if the person leaves the company

Write it as a clear discussion document, not a finished contract.
At the end, give me a list of questions the two of us need to
answer, and a note on which points I should bring to a lawyer —
this isn't legal advice, and I want to know where I need one.