Accepting the Right Suggestions

What it is for

Some suggestion classes are always right — agreement, tense, real typos. Others quietly flatten rhythm and hedge every strong sentence. This sorts them, so accepting suggestions in bulk stops costing you the writing.

The skill Copy

Not all suggestions are the same kind of thing. Sort them before accepting.

**Always accept** — these are errors and have no upside:
- Spelling, subject-verb agreement, duplicated words, wrong homophone.
- Punctuation inside quotes, missing article, tense slip.

**Read, then decide** — these change meaning:
- "Wordy" on a sentence carrying a qualification. The qualification may be the
  point, and removing it makes a hedge into a claim.
- Passive-to-active where the actor is genuinely unknown or unimportant.
  "The file was deleted" is honest when you do not know who deleted it.

**Usually reject** — these flatten:
- Splitting a long sentence that is long because the idea has parts.
- Replacing a specific word with a common one. "Dropped by 40%" is not
  improved by "decreased".
- Tone suggestions on anything with bad news in it. Softening a real problem
  is how a status update stops being useful.

Turn off the goal-based tone rewriting for technical writing. It optimises for
"confident and friendly", which is the wrong register for a bug report.

How to install it Copy

1. Open the tool and start a new conversation, project or template.
2. Paste the text below wherever the tool keeps standing instructions
   — usually called system prompt, instructions, or persona.
3. Save it so it applies to every run rather than a single message.

Did it work for you?

Where it came from