Select & Transform
Point at It, Don't Describe It
Select text, pick an action from the floating toolbar, see changes as inline diffs with accept/reject. No need to describe which text to change — just point at it.
Framing
The problem
Describing the exact target of an edit is slower than pointing at it.
The pattern
Turn selection into AI scope and render changes as reviewable diffs.
Why chat breaks here
Users must verbally restate location, boundaries, and transformation intent.
Risks
Local transforms can distract from structural problems that need broader revision.
Avoid when
The task requires holistic rewriting rather than scoped changes.
Use when
Edits target a specific span and naming the location verbally would be slower than pointing.
DOPE evaluation
- Directability
- Selection sets the scope, the floating toolbar names the verbs, and each diff carries its own accept/reject — edits are approved one at a time, not as a bundle
- Observability
- Every transform renders as an inline diff — struck-through original above the replacement — so the change is visible before it becomes the text
- Predictability
- The blast radius is the selection: "Simplify" touches the highlighted sentence and nothing outside it, unlike a chat rewrite that reflows the whole paragraph
- Explainability
- Each pending diff is tagged with the action that produced it, so "why did this sentence change" is answered by a label, not reconstruction
In the wild
- Apple Intelligence Writing Tools (Apple) — Select text → Writing Tools → Rewrite / Friendly / Professional / Concise / custom description, with original-version toggle as the diff-style review.
- Notion AI (Notion) — Select text → "Ask AI to edit" → in-place edit with diff confirmation. The agent edits in the doc on selection, not in a side panel.
- Cursor Cmd+K (Cursor) — Inline editing — select code, press Cmd+K, describe the change, see red/green inline diff with accept/reject. Hero example for code.
FAQ
When should I use the Select & Transform pattern?
Edits target a specific span and naming the location verbally would be slower than pointing.
When should I avoid the Select & Transform pattern?
The task requires holistic rewriting rather than scoped changes.
What problem does Select & Transform solve?
Describing the exact target of an edit is slower than pointing at it.
Why is chat the wrong fit for this?
Users must verbally restate location, boundaries, and transformation intent.
Related patterns
- Often paired with: Ghost Text Editor — Predict next sentence, then point at any text to reshape it precisely.
- Often paired with: Parallel Alternatives — Transform a selection into three variants you can compare or blend.
- Alternative to: Tone of Voice — Targeted edit on selected text vs global stylistic dial for the whole doc.