Use case · language and tone
Write a social reply in another language.
Describe the point you want to make, request a language in the instructions field, then review the meaning and level of formality. A fluent draft can still say the wrong thing.
A careful way to use the draft
- Open a supported desktop social comment box and decide what you want to say in your own words.
- Open ReplyPilot with
/rp. Ask for the target language in Custom Instructions, choose a tone, then generate a draft. - Read the draft for meaning, names, technical terms, formality, and local expressions. Ask a fluent reviewer when nuance matters.
- Edit the result and publish only when it represents your own intent. Clear or update Custom Instructions before a different writing task.
Review meaning before polishing style
- Compare the draft with your original point. Check questions, negations, dates, quantities and any commitment attributed to you.
- Check terms and register. A technical label or a formal pronoun can change how a reply is understood even when the sentence is fluent.
- Ask a fluent reviewer when the stakes or ambiguity require it. If you cannot verify the meaning, simplify the reply or use a language you can review confidently.
Instructions can persist in the extension. Clear the language request before your next task if it no longer applies. This workflow is a draft for you to check, not a guarantee of perfect translation.
When another tool is a better fit
If you are continuing a one-to-one message thread and the history with that person matters more than the public comment, Grais describes relationship memory and language support for that messaging job. See the ReplyPilot vs Grais comparison.