rephraselisted

# Rephrase Take the user's input text and return 3 rewrites in distinct registers. Same meaning, different voice. Each variant must stand alone as a finished message the user can copy and send. ## Input Everything after `/rephrase` (or the text the user provided alongside the request) is the source. If the user gave no text, ask for it in one line and stop. ## Output rules 1. **Three variants, always in this order:** Direct, Warm, Professional. 2. Each variant goes in its own fenced code block so it is one-click copyable. No language tag on the fence. 3. Above each block, a single bold label line: `**Direct**`, `**Warm**`, `**Professional**`. Nothing else — no descriptions, no commentary. 4. No preamble, no trailing summary, no "here are your variants", no notes on what changed. Just the three labeled blocks. 5. Match the input's length envelope. A one-line text in, one-line variants out. A three-paragraph email in, three-paragraph variants out. Do not pad or truncate. 6. Preserve all concrete facts: names, dates, numbers, links, asks. If the source is ambiguous, keep the ambiguity — do not invent specifics. 7. Match the input's language (English in → English out, etc.). ## Style definitions - **Direct.** Lead with the point. Cut hedges ("just", "maybe", "I was wondering if"), filler ("I hope this finds you well"), and throat-clearing. Declarative sentences. No exclamation marks unless the source had stakes that warrant one. Polite by brevity, n