Add tone adjustment controls for AI-generated content

[jeffpaul]

Explore adding tone or style controls (for example: casual, formal, technical) to AI-generated and AI-rewritten content in the editor. This would allow users to guide the voice of generated text without manual prompt editing.

This should be designed as an experiment and built on top of existing Abilities and prompt infrastructure.

Acceptance criteria:

• Define supported tone options and how they are selected in the UI
• Tone selection influences AI output consistently
• Implementation works across relevant editor experiments
• Extensible for additional tones or styles in the future

[itsgajendraSingh]

Hi @jeffpaul 👋 I'd love to work on this!

My plan:

• Define a tones.js config with extensible tone options (casual, formal, technical, etc.)
• Build a ToneSelector UI component for the editor
• Inject the selected tone into the existing prompt infrastructure

Could you assign this to me?

[jeffpaul]

@itsgajendraSingh before jumping into implementation, it would be helpful to have some rough wireframes or userflows or even just simple mockups of how the UI could look/work. If you're able to work on that, or have a friend or colleague who could, then let's start there to get a light agreement on user-facing approach and after that can dive into the implementation here.

[itsgajendraSingh]

Thanks for the direction.

I put together a rough wireframe to visualize one possible approach, but before going deeper I wanted to flag something I am not sure about.

1. The tone selector lives inside a PluginDocumentSettingPanel in the sidebar, consistent with how Excerpt Generation and Content Summarization are already surfaced.

2. The user picks a tone from a simple dropdown (Casual, Formal, Technical, Persuasive, Creative, Friendly) and triggers a rewrite.

3. The suggestion appears inline so the user can review and either accept or discard it, keeping the same manual review approach the plugin already follows.

You will notice the wireframe includes an "Apply to" scope selector with options like selected text, current paragraph, and entire post. That is based on one interpretation of the issue, which is exactly what my question below is about.

When you mention "AI-generated and AI-rewritten content", are you thinking about tone as a modifier for the existing experiments like Title Generation and Content Summarization? Or is the idea to also add a standalone tone-based rewrite capability for body content?

I ask because the wireframe assumes the second interpretation, which would require building new rewrite functionality on top of the existing prompt infrastructure. If the intent is closer to the first, the scope would be simpler and we could just thread tone controls into the experiments that are already there.

Would love your thoughts before going any further!

[jeffpaul]

@karmatosed curious for your input here, especially as there are a couple text-based generation options in the plugin (Title, Excerpt, Alt Text, Content Summary) and whether this tone adjustment should attempt to target each of those or a subset?