AddThisFeature

AI Tone Adjustment

Shift text toward a professional, friendly, direct, confident, or empathetic register.

moderate AI Content

What it adds

A tone selector over a text selection that proposes a re-registered version with the facts and the request unchanged.

What your agent is told to do

5
  1. 1

    Offer a short closed list of tones and no free-text option. Each tone must have a written definition in the prompt so the same choice produces a consistent register across the app.

  2. 2

    Hold the substance fixed. The request being made, the answer being given, the facts, and the figures must survive the shift unchanged; only phrasing, register, and hedging may move.

  3. 3

    Show the adjusted text next to the original and require an explicit accept before it replaces anything. Tone is subjective, so the user must be the one who decides the result is better.

  4. 4

    Let a workspace mark passages as locked — regulated disclosures, legal notices, standard clauses — and pass those through untouched, excluding them from the adjustable range entirely.

  5. 5

    Restructuring for clarity or length belongs to AI Text Rewriting and error detection belongs to AI Grammar and Clarity Review. This feature owns register only; reuse the selection, preview, and accept mechanism the rewrite feature already provides.

Edge cases it handles

8
  • A friendlier version of a refusal is still a refusal. The concrete facts and the actual request must be present in the output, and a result that has dropped either must be rejected rather than shown.
  • Tone instructions push models toward caricature: stereotyped register, performative warmth, or stacked exclamation. Constrain the output to plain professional prose and reject theatrical results.
  • Locked regulated or legal wording must come through byte-for-byte. Verify it after generation, because a prompt instruction alone is not a guarantee.
  • Nothing may be replaced without a preview. Tone changes look small in a diff and large to a recipient, so the user must see both versions before committing.
  • Making bad news sound positive is the characteristic failure of this feature. A message conveying a delay, a rejection, or a problem must still read as one after an empathetic or confident adjustment.
  • Applying two tones in succession compounds drift away from the original. Always adjust from the stored original rather than from the previous adjustment.
  • A refusal, a timeout, or output that comes back truncated must leave the original text in place and say so plainly.
  • With the model unavailable the tone control is disabled with a reason and the editor is otherwise unaffected.

Definition of done

9
  • Tones come from a closed, documented list with consistent definitions.
  • Facts, figures, and the underlying request are preserved and verified against the source.
  • Passages marked locked are returned unchanged and confirmed unchanged after generation.
  • No adjusted text replaces the original without a side-by-side preview and an explicit accept.
  • A message carrying bad news still reads as such after adjustment.
  • Successive adjustments start from the stored original, not the previous output.
  • Model failure leaves the text untouched.
  • The feature matches the existing design system.
  • No existing functionality is broken.

Related features

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 3

    It inspects, then implements

    Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.