11KB
Coffee Chat Editor
Version: 1.0.0 Status: ACTIVE
Purpose
Edit AI-generated or overly formal prose so it sounds direct, natural, specific, and human while preserving the author's intended meaning.
The goal is not:
MAKE EVERYTHING CASUAL
The goal is:
REMOVE MECHANICAL AI WRITING
while retaining the appropriate level of professionalism.
1. Trigger Conditions
Use this skill for important user-facing prose such as:
- emails
- reports
- proposals
- executive updates
- documentation
- announcements
- instructions
- presentations
- business communication
- explanations
- public-facing copy
Use it when the draft sounds:
generic
stiff
repetitive
overly formal
corporate
AI-generated
wordy
Do not apply this style mechanically to:
- source code
- legal text that must preserve exact wording
- technical specifications where precision requires formality
- quoted source material
- data tables
2. Core Editing Pass
Use this sequence:
CUT
↓
SPECIFY
↓
SIMPLIFY
↓
VARY
↓
SPEAK
3. Cut Unnecessary Opening
Look at the first sentence or paragraph.
Common weak openings:
Certainly!
Great question.
In today's rapidly evolving world...
It is important to note that...
I hope this message finds you well...
Ask:
Does the reader need this before the real message?
If not, remove it.
Start closer to the point.
4. Cut Unnecessary Closing
AI prose often repeats itself at the end.
Example:
In conclusion, by following these steps,
you can ensure a successful implementation.
If the body already established this, remove it.
A useful ending may instead contain:
decision
next action
deadline
specific request
important final fact
5. Replace Generic Language
Weak:
We encountered some challenges during implementation.
Better:
The import failed because 214 rows contained invalid ZIP codes.
Prefer:
CONCRETE FACT
over:
GENERIC DESCRIPTION
6. Replace Generic Verbs
Weak verbs include:
utilize
facilitate
leverage
enable
optimize
enhance
when a simpler verb communicates more clearly.
Examples:
utilize → use
facilitate communication → help the teams communicate
leverage the API → use the API
Do not ban a word if it is genuinely the most accurate choice.
7. Remove Transitional Slag
Look for excessive:
Furthermore
Moreover
Additionally
In addition
With that being said
As previously mentioned
It is worth noting
Sometimes the next sentence can simply begin.
Transitions should clarify structure, not fill space.
8. Vary Sentence Length
Mechanical AI writing often has repeated sentence rhythm.
Example:
The system validates the request.
The system checks the database.
The system creates the record.
The system returns the response.
Possible revision:
The system validates the request, checks the database,
and creates the record. If successful, it returns the response.
Do not artificially vary sentences merely to create style.
Prioritize readability.
9. Prefer Active Voice
Weak:
The database was updated by the deployment script.
Better:
The deployment script updated the database.
Use passive voice when the actor is:
unknown
irrelevant
intentionally de-emphasized
Active voice is a preference, not an absolute rule.
10. Replace Abstract Nouns
Weak:
The implementation of the validation will provide
an improvement in reliability.
Better:
The validation will make the import more reliable.
Look for unnecessary noun constructions:
implementation of
utilization of
optimization of
execution of
Convert to direct verbs when possible.
11. Remove Fake Importance
Watch for:
crucial
critical
paramount
pivotal
essential
game-changing
when no evidence supports the emphasis.
Weak:
It is crucial to ensure robust data integrity.
Better:
Validate the imported row count before deleting the source file.
Specific consequences create importance naturally.
12. Avoid Decorative Vocabulary
Be suspicious of words that make simple ideas sound grand.
Examples:
delve
landscape
tapestry
multifaceted
spearhead
unlock
foster
synergy
seamless
navigate
Do not maintain a rigid banned-word list.
The real rule is:
USE THE SIMPLEST ACCURATE WORD
13. Reduce Artificial Symmetry
AI frequently writes:
faster, smarter, and more efficient
clear, concise, and actionable
security, scalability, and reliability
Three-part lists are fine when three real categories exist.
Remove them when they are decorative.
14. Reduce Excessive Headings
Do not create a heading for every paragraph.
Use headings when they help the reader:
scan
navigate
understand hierarchy
For short communication, paragraphs may be better.
15. Reduce Excessive Bold
AI drafts often bold too many phrases.
Use emphasis for genuinely important:
decision
deadline
risk
action
number
If everything is emphasized, nothing is.
16. Keep Specific Numbers
Do not replace:
214 rejected rows
with:
a number of rejected records
Specific information makes prose sound more credible and useful.
17. Keep Necessary Technical Terms
Do not simplify away precision.
Example:
TLS certificate
should not become:
security thing
Use the proper term and explain it when the audience needs help.
18. Remove Repetition
Check whether consecutive sections repeat:
same conclusion
same risk
same recommendation
same background
Merge or cut repetition.
19. Compress Setup
Weak:
Before we get into the details, it may be useful to first
provide a little bit of context regarding how the system
currently operates.
Better:
The application currently imports the CSV directly into Access.
Start with actual context.
20. Direct Requests
For email or business communication, make the requested action obvious.
Weak:
It would be greatly appreciated if you could potentially
review the attached material when you have an opportunity.
Better:
Please review the attached file by Friday.
Direct does not mean rude.
21. Friendly Without Filler
Warm communication may still be concise.
Example:
Thanks again for helping with the convention cleanup.
The windows looked great, and your help made Friday's setup much easier.
This is warmer than generic praise because it is specific.
22. Tone Levels
Choose a tone appropriate to the audience.
Level 1 — Executive Brief
Use:
short
decision-focused
specific
little background
Level 2 — Peer Colleague
Use:
direct
professional
natural
moderate technical detail
Level 3 — Socratic Tutor
Use:
clear
conversational
question-driven
supportive without overpraise
Level 4 — Non-Technical Friend
Use:
plain language
short examples
minimal jargon
natural phrasing
Do not automatically choose Level 4 because it sounds “human.”
Audience determines tone.
23. Executive Editing Example
Before:
It is important to note that the deployment was ultimately
successful, despite the fact that we did encounter a number
of challenges throughout the overall implementation process.
After:
The deployment succeeded after we corrected two configuration errors.
24. Technical Documentation Example
Before:
In order to facilitate the process of determining which
application is currently utilizing a specific port, the
following command can be leveraged.
After:
Use this command to find the process using a port:
25. Status Update Example
Before:
We have continued to make meaningful progress across a
number of key areas as we navigate toward completion.
After:
The API is complete. Database migration testing is still in progress.
26. Email Example
Before:
I just wanted to reach out and take a moment to thank
everyone for all of your assistance and support.
After:
Thank you for helping with the cleanup this weekend.
Specific detail can follow.
27. Do Not Destroy Personality
The goal is not to make every writer sound identical.
Preserve:
humor
warmth
formality
directness
individual vocabulary
when appropriate.
Remove machine-like patterns, not human personality.
28. Do Not Over-Compress
Too much editing can turn useful explanation into telegram-style prose.
Before:
The script stops IIS before copying the files because
IIS may otherwise keep DLLs open and prevent replacement.
Do not reduce to:
Stop IIS. Copy files.
The explanation matters.
29. Read-Aloud Test
After editing, mentally read the prose at speaking pace.
Ask:
Would a real person naturally say this?
Is any sentence awkward?
Is any phrase unnecessarily formal?
Does the rhythm sound repetitive?
This is a strong final test.
30. Meaning Preservation
Never change:
technical meaning
commitment
deadline
legal meaning
risk severity
quantitative facts
merely to improve tone.
Stylistic editing must preserve substance.
31. Source Preservation
When editing text based on a provided source, preserve the source's:
facts
claims
terminology
level of certainty
Do not introduce unsupported content merely to make the prose sound more complete.
32. Five-Step Fast Pass
For routine editing, use:
1. CUT unnecessary first/last sentence
2. VARY repetitive sentence structure
3. REPLACE generic language with specifics
4. REMOVE mechanical transitions
5. READ ALOUD
This is the default lightweight mode.
33. Full Pass
For important external communication:
1. identify audience
2. identify purpose
3. identify required action
4. remove unnecessary preamble
5. replace generic language
6. simplify verbs
7. remove repetitive transitions
8. vary sentence length
9. check technical precision
10. check tone
11. remove redundant closing
12. read aloud
34. Output Contract
When used as an editing skill, return:
EDITED VERSION
When useful, also briefly identify:
major changes made
Do not bury the revised text underneath a long critique unless critique was requested.
35. Self-Improvement
Improve this skill when:
- edited output still sounds mechanical
- editing removes too much technical precision
- tone becomes overly casual
- repeated user corrections reveal a stable writing preference
- a better concise editing checklist emerges
Do not create enormous word-ban lists.
Prefer principles.
36. Changelog
1.0.0
Initial active version.
Introduced:
- zero-preamble preference
- unnecessary-ending removal
- concrete specificity
- active voice
- transition cleanup
- sentence-rhythm variation
- anti-buzzword guidance
- tone levels
- read-aloud test
- meaning preservation
- five-step fast pass