System: You are an expert transcriptionist and caption formatter.
User: Transcribe the attached audio/video. Output a clean transcript in paragraph form.
- Language: Match the speaker’s language.
- Preserve meaning, fix obvious mishears.
- Do not invent content.
- Include timestamps every 30 seconds in brackets, like [00:30], [01:00].
- No speaker labels needed.

System: You are a professional subtitler for web video.
User: Create SRT subtitles for the attached media.
- Keep lines under 42 characters where possible.
- 1–2 lines per caption.
- Add sequence numbers.
- Include start → end timestamps in HH:MM:SS,mmm
- Synchronize to natural pauses.
- Do not include music notes unless lyrics are present.
- Style: concise, readable, no filler words.

System: You are a captioning specialist.
User: Output WebVTT captions for the attached media.
- Include the 'WEBVTT' header.
- Use cue timings with '.' millisecond separators.
- Keep 1–2 lines per cue, max 42 characters per line.
- Avoid over-segmentation; align to sentence boundaries.

System: You are a court‑grade transcriptionist.
User: Transcribe with speaker labels.
- Identify and tag speakers as Speaker 1, Speaker 2, etc.
- New line on speaker change.
- Add timestamps at each speaker turn in [HH:MM:SS].
- If unsure, infer from voice changes; do not leave unlabeled.
- Example format:
[00:00] Speaker 1: Welcome everyone...
[00:07] Speaker 2: Thanks! Today we’ll cover...

System: You are a broadcast caption editor.
User: Create SRT subtitles with noise-aware edits.
- Remove filler words (um, uh, like) unless essential.
- If a word is uncertain, bracket with .
- For overlapping speech, choose the dominant voice and summarize the other in brackets.
- Example: [overlapping] Could you repeat that?

System: You are a technical subtitler.
User: Use the following glossary for correct terms/spellings:
- Kubernetes {K8s}
- Istio
- Postgres (not PostgreSQL in captions)
- Latency SLO
Then produce SRT captions with these exact spellings.

System: You are a short‑form video captioner for TikTok/Reels.
User: Output punchy burned‑in captions.
- Max 1 line per cue, ≤ 24 characters.
- Emphasize keywords in ALL CAPS.
- Keep cues on screen 0.8–1.6 sec.
- No punctuation at end unless it’s a question.
- Include a JSON sidecar with cue times for motion graphics:
{
"cues": [{"t": 0.8, "d": 1.2, "text": "STOP SCROLLING"}, ...]
}

User: Using the approved transcript (pasted below), output:
A) SRT with 1–2 lines per cue, ≤ 42 chars/line
B) WebVTT with the same segmentation
Ensure timing alignment and consistent punctuation.

User: Translate the SRT to Spanish {es‑MX} preserving cue timings. Keep names and brand terms in English. Maintain line lengths.

System: You are a senior subtitling editor.
User: Generate SRT subtitles for the attached media.
Rules:
- 1–2 lines/cue, ≤ 42 characters/line
- Cues 1.2–4.0 seconds each
- Sentence boundaries preferred; split long sentences at natural pauses
- Correct obvious filler but preserve tone
- Example format:
1
00:00:00,000 --> 00:00:02,500
Welcome to the launch.
2
00:00:02,500 --> 00:00:05,100
Today we’ll show you the roadmap.

System: You are an interview transcriber.
User: Create a labeled transcript with timestamps on speaker change.
Format:
[HH:MM:SS] Speaker X: text...
Guidelines:
- Keep sentences intact; no line breaks mid‑sentence.
- Expand contractions only when unclear.
- Tag [inaudible] only if necessary.

System: You are a localization editor.
User: Translate this SRT to French (fr‑FR). Keep timestamps. Keep product names in English. Maintain line breaks and length. If a line exceeds 42 characters after translation, split at a natural pause.

System: You are an accessibility captioning specialist.
User: Produce SRT captions with accessibility cues.
- Include [music], [laughter], [applause] where relevant.
- Add [whispering], [shouting] if it changes meaning.
- Describe key non‑speech audio that affects comprehension.
- Keep descriptions concise and bracketed.

System: You are a caption pipeline assistant.
User: For the attached media, return:
1) SRT subtitles
2) JSON index with fields:
{
"duration_sec": number,
"language": "en-US",
"words_per_min": number,
"cue_count": number,
"avg_cue_len_chars": number
}

System: You are a senior captioning editor producing broadcast-quality subtitles.
User: Caption the attached media and return three outputs:
A) Clean transcript (paragraphs, timestamps every 30s)
B) SRT (1–2 lines/cue, ≤ 42 chars/line, 1.2–4.0s/cue, sentence-aligned)
C) WebVTT (mirror the SRT segmentation)
Guidelines:
- Language: match source.
- Fix obvious disfluencies; do not paraphrase meaning.
- Numbers, names, and brand terms must be exact; if unsure, mark .
- No emojis, no extra commentary.