Write clear, emotionally resonant, and well-structured content that readers remember and act upon. Use when writing or editing any text—Twitter posts, articles, documentation, emails, comments, updates—for maximum clarity, engagement, and impact.
Transform any content into clear, memorable, and actionable text using research-backed principles that work across all platforms and contexts. This skill synthesizes 50+ years of readability research, neuroscience of memory, and platform engagement studies into practical techniques.
Core insight: The same psychological principles drive engagement everywhere—clarity reduces cognitive load, specificity creates memory, and structure enables scanning. Master these universal patterns and apply them to any writing context.
These evidence-based principles work across all platforms and contexts.
Sentence length determines comprehension:
Target: 15-20 words average, 25 words maximum per sentence.
Word choice matters:
79% of readers scan rather than read. Design for this reality:
Stories trigger oxytocin release, enabling empathy and memory formation:
Specific details outperform vague statements:
Example transformation:
Before: "I learned a lot from this experience and want to share some thoughts"
After: "5 hard lessons from shipping 10,000 lines of code in 48 hours:"
Use this checklist for any content revision:
Clarity Pass:
- [ ] Average sentence length < 20 words
- [ ] No sentence > 30 words
- [ ] Passive voice < 10% of sentences
- [ ] Jargon replaced with simple alternatives
Structure Pass:
- [ ] Opening hook captures attention
- [ ] Key message in first paragraph
- [ ] Headings every 3-4 paragraphs (for longer content)
- [ ] Bullet points for lists of 3+ items
- [ ] Clear call-to-action or takeaway at end
Conciseness Pass:
- [ ] Removed "very," "really," "quite," "just"
- [ ] Replaced multi-word phrases with single words
- [ ] Deleted redundant explanations
- [ ] Cut 10-30% from original word count
Common phrases to simplify:
| Wordy | Concise |
|---|---|
| due to the fact that | because |
| in order to | to |
| at this point in time | now |
| in the event that | if |
| with regard to | about |
| a large number of | many |
| in spite of the fact that | although |
| for the purpose of | to |
Complex words to simplify:
| Complex | Simple |
|---|---|
| utilize | use |
| commence | start |
| terminate | end |
| demonstrate | show |
| facilitate | help |
| subsequent | later |
| approximately | about |
| endeavor | try |
Opens with a question the reader wants answered:
"What if everything you knew about productivity was wrong?"
Opens with surprising data:
"90% of visitors who read your headline also read your CTA—yet most writers spend 10x more time on body copy."
Opens with a brief narrative:
"At 3 AM, with the deploy failing for the sixth time, I realized the bug wasn't in the code."
Opens with a bold statement:
"Most advice about writing is wrong. Here's what actually works."
Challenges an assumption:
"The best writers don't write more. They delete more."
Content that sticks follows these patterns:
Implication: Put most important points first and last.
Violated expectations create distinctive memories:
Before: "The meeting went exactly as planned."
After: "The meeting started with our CEO apologizing. In 15 years, I'd never seen that."
Activates multiple brain regions:
Before: "The code was messy."
After: "The code sprawled like tangled Christmas lights—one pull and everything breaks."
Problem: Explaining what readers already know Fix: Assume intelligence, provide only new information
Problem: Key point in paragraph 3 Fix: Move conclusion to opening, support with details
Problem: Dense paragraphs without visual breaks Fix: Add headings, bullets, white space
Problem: "Mistakes were made" (who made them?) Fix: "The team missed the deadline" (clear ownership)
Problem: "We synergized cross-functional paradigms" Fix: "We got the teams to work together"
Classic persuasion structure that works for any content with a goal:
Attention: "Most developers waste 3 hours/day on preventable bugs."
Interest: "Static analysis catches 85% of these before they ship."
Desire: "Teams using this approach ship 2x faster with fewer incidents."
Action: "Add this one-line config to your CI pipeline."
Effective for blog posts, landing pages, and persuasive content:
Problem: "Your documentation is outdated the moment you write it."
Agitate: "New devs waste days. Senior devs answer the same questions. Nobody trusts the docs."
Solution: "Generate docs from code comments. Always current, always trusted."
Transformation narrative that creates emotional resonance:
Before: "I spent 6 hours debugging a production issue."
After: "Now I catch these problems before they deploy."
Bridge: "Here's the monitoring setup that changed everything."
For instructional content—simple, scannable, actionable:
1. The Problem: What's wrong and why it matters
2. The Solution: What to do about it
3. The How: Specific steps to implement
For deeper guidance on specific topics:
C - Concise: Cut 10-30% without losing meaning L - Lead with value: Key point in first sentence E - Evidence-based: Specific data beats vague claims A - Active voice: Subject-verb-object structure R - Reader-focused: What do they need to know?
After writing, verify:
If any test fails, revise that section.