impactful-writing
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.
Install
npx skills add https://github.com/tenequm/skills/tree/main/skills/impactful-writing
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install tenequm-skills@llmmart
git clone https://github.com/tenequm/skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole tenequm/skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Impactful Writing
Overview
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.
When to Use This Skill
- Writing or editing Twitter/X posts, threads, or social content
- Creating blog posts, Medium articles, or long-form content
- Drafting documentation, README files, or technical writing
- Composing emails, Slack messages, or professional communication
- Writing GitHub comments, PR descriptions, or code reviews
- Creating update messages, announcements, or change logs
- Editing any existing content for clarity and impact
Universal Writing Principles
These evidence-based principles work across all platforms and contexts.
1. Clarity Through Simplicity
Sentence length determines comprehension:
- 14 words: 90%+ reader comprehension
- 25 words: Difficulty begins
- 43 words: <10% comprehension
Target: 15-20 words average, 25 words maximum per sentence.
Word choice matters:
- Simple words process 76% faster than jargon
- Active voice processes 15-20% faster than passive
- Concrete beats abstract (activates sensory brain regions)
2. Structure for Scanning
79% of readers scan rather than read. Design for this reality:
- Front-load key information (inverted pyramid)
- Use descriptive headings every 3-4 paragraphs
- Keep paragraphs to 3-5 sentences maximum
- Use bullet points for 3+ related items
- Optimal line length: 50-75 characters
3. Emotional Resonance
Stories trigger oxytocin release, enabling empathy and memory formation:
- Open with a hook (question, surprising fact, brief story)
- Use sensory, concrete language
- Create curiosity gaps (specific questions readers want answered)
- Close with memorable takeaways (recency effect)
4. Specificity Over Abstraction
Specific details outperform vague statements:
- "45% increase" beats "significant growth"
- "in 5 minutes" beats "quickly"
- "10 ways" beats "several ways"
- Concrete examples beat abstract explanations
Quick Start Workflow
Writing New Content
- Define the core message in one sentence
- Open with a hook (question, fact, or story)
- Structure with headings for scannability
- Use short sentences (15-20 words average)
- Close with clear takeaway or call-to-action
Editing Existing Content
- Read aloud to identify awkward passages
- Cut word count by 10-30% without losing meaning
- Convert passive to active voice
- Replace jargon with simple words
- Add structure (headings, bullets, white space)
Platform-Specific Guidance
Twitter/X Posts
- Optimal length: 71-100 characters for engagement
- Hook in first line: Must capture in 3 seconds
- Use numbers: "10 lessons" outperforms "lessons learned"
- Thread structure: Each tweet must stand alone AND connect
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:"
Blog Posts / Articles
- Optimal reading time: 7-10 minutes
- Headings: Every 300-500 words
- First paragraph: Must deliver the promise
- Conclusion: Summarize key points, provide clear next step
Technical Documentation
- Lead with the goal: What will the reader accomplish?
- Show, don't tell: Working code examples beat explanations
- Progressive disclosure: Basic → Advanced
- Consistent terminology: One term per concept
Professional Communication (Email/Slack)
- Subject lines: Specific over clever ("Q4 Report Draft" > "Quick update")
- One topic per message: Increases response rate
- Front-load action items: Don't bury the ask
- Keep to half-page maximum: Longer = lower read rate
GitHub Comments / PR Descriptions
- Start with context: What problem does this solve?
- Use bullet lists: For changes, decisions, trade-offs
- Include "why": Reasoning > description
- Be direct but kind: Critique code, not people
The Revision Checklist
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
Word Reduction Patterns
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 |
Hook Patterns That Work
Question Hook
Opens with a question the reader wants answered:
"What if everything you knew about productivity was wrong?"
Statistic Hook
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."
Story Hook
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."
Declarative Hook
Opens with a bold statement:
"Most advice about writing is wrong. Here's what actually works."
Contradiction Hook
Challenges an assumption:
"The best writers don't write more. They delete more."
Memory and Impact Principles
Content that sticks follows these patterns:
Serial Position Effect
- First items: ~70% recall (primacy)
- Last items: ~60% recall (recency)
- Middle items: ~40% recall
Implication: Put most important points first and last.
Prediction Errors
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."
Sensory Language
Activates multiple brain regions:
Before: "The code was messy."
After: "The code sprawled like tangled Christmas lights - one pull and everything breaks."
Common Anti-Patterns
Over-Explaining
Problem: Explaining what readers already know Fix: Assume intelligence, provide only new information
Buried Lede
Problem: Key point in paragraph 3 Fix: Move conclusion to opening, support with details
Wall of Text
Problem: Dense paragraphs without visual breaks Fix: Add headings, bullets, white space
Passive Avoidance
Problem: "Mistakes were made" (who made them?) Fix: "The team missed the deadline" (clear ownership)
Jargon Cascade
Problem: "We synergized cross-functional paradigms" Fix: "We got the teams to work together"
Proven Content Frameworks
AIDA (Attention → Interest → Desire → Action)
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."
PAS (Problem → Agitate → Solution)
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."
BAB (Before → After → Bridge)
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."
1-2-3 Structure
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
Detailed References
For deeper guidance on specific topics:
- references/clarity-science.md: Research on readability, cognitive load, and plain language with specific metrics
- references/emotional-impact.md: Neuroscience of storytelling, memory, and persuasion
- references/structure-patterns.md: Eye-tracking research, scanning patterns, and formatting
- references/revision-frameworks.md: Professional editing processes and before/after examples
Quick Reference: The CLEAR Framework
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?
Validation: Content Quality Check
After writing, verify:
- Core message test: Can you state it in one sentence?
- So what test: After each paragraph, can you answer "so what"?
- Grandmother test: Would a non-expert understand the main point?
- Action test: Does the reader know what to do next?
- Cut test: Can you remove any sentence without losing meaning?
If any test fails, revise that section.
Files (skills)
-
references
-
clarity-science.md 8 KB
# The Science of Writing Clarity Research-backed principles for maximum comprehension and readability. ## Contents - Sentence Length Research - Readability Metrics - Cognitive Load Theory - Plain Language Studies - Active vs Passive Voice - Word Complexity Research ## Sentence Length Research ### American Press Institute Study Comprehension rates by sentence length: - **8 words or less**: Very easy (near 100% comprehension) - **14 words**: 90%+ comprehension (optimal) - **17 words**: Standard difficulty - **21 words**: Fairly difficult - **25 words**: Difficult (comprehension drops significantly) - **43 words**: Less than 10% comprehension ### Screen Reader Accessibility Study (2020) 21 blind participants tested sentence lengths with screen readers: - **16-20 words**: Highest comprehension, lowest cognitive workload - **Over 25 words**: Significant comprehension impairment ### Practical Guidelines **Target Averages:** - General audience: 15-20 words - Professional audience: 18-22 words - Technical content: 20-25 words maximum **Variation is key**: Mix short (5-10), medium (15-20), and occasional longer sentences (25-30) for rhythm. ## Readability Metrics ### Flesch Reading Ease (FRE) Scale: 0-100 (higher = easier) | Score | Reading Level | Example | |-------|--------------|---------| | 90-100 | 5th grade | Very easy, understood by 11-year-old | | 80-90 | 6th grade | Easy, conversational | | 70-80 | 7th grade | Fairly easy | | 60-70 | 8th-9th grade | Standard (optimal for most content) | | 50-60 | 10th-12th grade | Fairly difficult | | 30-50 | College | Difficult | | 0-30 | College graduate | Very difficult | **Formula factors:** - Average sentence length (words per sentence) - Average syllables per word ### Flesch-Kincaid Grade Level Estimates US grade level required to understand text. **Targets by audience:** - General public: 6th-8th grade - Business communication: 8th-10th grade - Technical professional: 10th-12th grade - Academic: 12th+ grade ### Validation 70+ years of research confirms these formulas work because: - Syllable complexity correlates with word familiarity - Sentence length correlates with cognitive load - Both are measurable and actionable ## Cognitive Load Theory ### Core Principles (John Sweller, 1980s) Three types of cognitive load: 1. **Intrinsic load**: Inherent complexity of the content (unavoidable) 2. **Extraneous load**: Mental effort from poor presentation (reducible) 3. **Germane load**: Productive effort building understanding (desirable) **Goal**: Minimize extraneous load to maximize comprehension. ### Working Memory Constraints George Miller's research (1956): - Working memory holds 5-9 "chunks" of information - Each clause or phrase competes for limited slots - Complex sentences overload working memory **Practical implications:** - One idea per sentence - Chunk related information together - Use headings to create mental categories ### Application to Writing **High extraneous load (avoid):** - Complex sentence structures - Jargon requiring mental translation - Dense paragraphs without visual breaks - Passive voice requiring agent identification **Low extraneous load (prefer):** - Simple subject-verb-object structure - Familiar vocabulary - Visual hierarchy with headings and lists - Active voice with clear actors ## Plain Language Studies ### Joseph Kimble's Research (50+ studies, 18 on legal documents) **Study 1: Judicial Opinions (251 lawyers)** - 61% preferred plain language versions - Average sentence reduction: 25 → 19 words (24%) - Rating improvement: 6/10 → 7/10 **Study 2: Lawsuit Papers (292 judges)** - 66% preferred plain English - 58% preferred informal plain English - Page reduction: 3.25 → 2.5 pages (23%) - Sentence reduction: 25.2 → 17.8 words (29%) **Study 3: Court Forms (controlled experiment, 60 participants)** - Plain language proof of service: 81% vs 61% accuracy (+33%) - Plain language subpoena: 95% vs 65% accuracy (+46%) - Document length reduction: ~40% **Study 4: FCC Marine Radio Rules (Government regulation)** - Correct answers: 10.66/20 → 16.85/20 (+58%) - Response time: 2.97 → 1.62 minutes (-45%) - Difficulty rating: 4.59/5 → 1.88/5 (-59%) ### Key Finding Plain language consistently outperforms complex prose across all reader types—including lawyers, judges, and specialists who work with complex language daily. ## Active vs Passive Voice ### Experimental Evidence Systematic review (2024) analyzing 9 studies: **Consistent findings:** - Active voice = reduced readability scores (easier) - Active voice = faster processing (15-20% improvement) - Active voice = higher comprehension scores - Active voice = fewer grammatical errors by readers - Active voice = rated as more coherent ### Cognitive Explanation Active voice matches natural language processing: - Brain expects: subject → verb → object - Passive requires mental reordering to identify agent - Additional transformation step consumes working memory ### When Passive is Acceptable Use passive voice only when: - Actor is unknown: "The window was broken" - Actor is irrelevant: "The experiment was conducted" - Object emphasis needed: "The proposal was rejected" - Hedging is appropriate: "Mistakes were made" **Default to active** in all other cases. ### Conversion Examples | Passive | Active | |---------|--------| | The report was written by the team | The team wrote the report | | Errors were found in the code | We found errors in the code | | The meeting was scheduled for 3pm | I scheduled the meeting for 3pm | | A decision was made to proceed | The board decided to proceed | ## Word Complexity Research ### Ohio State Jargon Study (2019, N=650) **Key finding**: Jargon reduced processing fluency by 76% even when definitions were provided. **Effects of jargon:** - Greater resistance to persuasion - Increased risk perceptions - Lower support for proposals - Effect persisted across multiple topics **Mechanism**: Jargon creates disfluency (difficult processing experience). Brain misattributes difficulty from jargon to the content itself, triggering skepticism. ### Syllable Reduction Impact Each syllable reduction improves readability scores: | Complex | Simple | Syllable Reduction | |---------|--------|-------------------| | utilize | use | 3 → 1 | | commence | start | 2 → 1 | | terminate | end | 3 → 1 | | demonstrate | show | 3 → 1 | | facilitate | help | 4 → 1 | | subsequent | later | 3 → 2 | | approximately | about | 5 → 2 | | endeavor | try | 3 → 1 | ### Compound Effect Small edits compound across documents: - 8,000-word document - Replace 50 complex words - Reduce 100 syllables - Improve readability by 1-2 grade levels - Increase comprehension by 10-20% ## Line Length Research ### Optimal Character Count **Desktop**: 50-75 characters per line (66 optimal) **Mobile**: 30-50 characters per line **WCAG Standard**: Maximum 80 characters ### Eye-Tracking Evidence (Baymard Institute) **Too long (100+ characters):** - Hard to focus on text - Difficult to find next line - Eye fatigue increases 43% - Comprehension drops 20% **Too short (<40 characters):** - Breaks reading rhythm - Causes premature line jumps - Increases cognitive load **Optimal range (50-75 characters):** - Natural eye movement - Subconscious energized at each line start - 28% improvement in reading speed ## Practical Application ### Before Writing 1. Define target audience reading level 2. Set readability goal (FRE 60-70 for general) 3. Plan average sentence length (15-20 words) ### During Writing 1. Write in active voice by default 2. Use familiar words over jargon 3. Limit sentences to one main idea 4. Break complex ideas into multiple sentences ### After Writing 1. Run readability analysis 2. Identify sentences over 25 words → split 3. Find passive constructions → convert 4. Replace complex words → simplify 5. Re-check readability score ### Validation Metrics Your content is optimized when: - Average sentence length: 15-20 words - Maximum sentence length: 25-30 words - Passive voice: <10% of sentences - Flesch Reading Ease: 60-70 (adjust for audience) - Flesch-Kincaid Grade: 8-9 (adjust for audience) -
emotional-impact.md 10 KB
# The Science of Emotional Impact Research on making content memorable, persuasive, and action-driving. ## Contents - Neuroscience of Storytelling - Memory and Retention - Hook Effectiveness - Word Choice and Emotion - Persuasion Principles - The Curiosity Gap ## Neuroscience of Storytelling ### Oxytocin and Narrative (Paul Zak, Claremont Graduate University) Stories trigger specific neurochemical responses: **Oxytocin**: Released when readers empathize with characters - Correlates with post-narrative prosocial behavior - Donations to charity increased 261% when oxytocin + attention combined - 82% predictive accuracy of post-story behavior from neurologic responses alone **Cortisol**: Rises during dramatic tension - Creates physiological engagement - Peaks at story climax **Dopamine**: Anticipation and reward - Released during uncertainty ("what happens next?") - Delivered at resolution ### Narrative Transportation Theory (Green & Appel, 2024) **Definition**: An experiential state of immersion where mental processes concentrate on narrative events. **Three components:** 1. Focused attention (suspending disbelief) 2. Emotional engagement (connecting with characters) 3. Mental imagery (visualizing the narrative world) **Measurable effects:** - Reduced counter-arguing (meta-analysis effect: r = .26) - Greater story recall one week later - Adoption of story-consistent attitudes and behaviors ### Character Identification Six dimensions drive character connection: 1. **Spatiotemporal**: Being in the story world 2. **Perceptual**: Seeing through character's eyes 3. **Cognitive**: Thinking like the character 4. **Moral**: Aligning values 5. **Emotional**: Feeling with the character 6. **Embodied**: Physical simulation **Key insight**: Readers rely on their own social-cognitive abilities, not just textual cues. Good writing provides scaffolding; reader empathy does the heavy lifting. ## Memory and Retention ### Serial Position Effect (Glanzer & Cunitz, 1966) | Position | Recall Rate | |----------|-------------| | First items (primacy) | ~70% | | Last items (recency) | ~60% | | Middle items | ~40% | **Application**: Put most important points at beginning and end. ### Emotional Arousal and Memory **McGaugh's research on the amygdala:** - Amygdala modulates memory consolidation in hippocampus - Emotional arousal enhances memory through amygdala-hippocampal phase coupling - Aversive/intense memories show stronger theta-phase coordination **Flashbulb memories** (Hirst & Phelps, 2016): - Highly emotional events create vivid, detailed memories - Not more accurate, but more confidently recalled - Mechanism: Emotional arousal → amygdala activation → enhanced consolidation ### Prediction Errors Enhance Memory **Sinclair & Barense research (2018, 2021):** - Violated expectations enhance memory encoding - Mnemonic prediction errors promote detailed, distinctive memories - Effect requires strong initial predictions—random surprises don't work **Mechanism**: Unexpected information disrupts hippocampal patterns, forcing new distinct memory traces rather than blending with existing knowledge. ### Distinctiveness and Specificity **Contrast effects** (Nature, 2024): - Higher-contrast information remembered ~15% better - Distinctive items stand out (Von Restorff effect) **Specificity enhances vividness** (Cooper et al., 2022): - Episodic memories rich in specific details rated as more vivid - Vividness correlates with hippocampal and angular gyrus activity **Practical insight**: Generic descriptions fade; specific sensory details create memorable mental simulations. ## Hook Effectiveness ### The Critical Window - **10-20 seconds** to capture initial interest - First sentence determines whether readers continue - Attention is a scarce neural resource (metabolically costly) ### Hook Types by Effectiveness **Question hooks**: Engage visualization and prediction - "What if everything you knew about X was wrong?" - Forces mental engagement to answer **Surprising statistics**: Provide concrete anchors - "90% of visitors who read your headline also read your CTA" - Violates expectations, creates curiosity **Brief personal stories**: Create identification - "At 3 AM, with the deploy failing for the sixth time..." - Triggers narrative transportation **Bold declarations**: Challenge assumptions - "Most advice about writing is wrong." - Creates prediction error, demands engagement ### BuzzSumo's 100M Headline Study **Top-performing patterns (2019-2020):** - Instructional language (#1): "you need to," "need to know" - Newness: "for the first time in X years" - Rankings: "of the year" (#1 most shared phrase) - Numbers: 10 is the most engaging number **Optimal headline length**: 11 words, 65 characters ## Word Choice and Emotion ### Concrete vs Abstract Language **Neuroimaging research findings:** **Concrete words** ("grasp," "caress," "savor"): - Activate sensory brain regions - Create stronger, more vivid neural pathways - Enable readers to "experience" descriptions **Abstract words** ("freedom," "creativity"): - Trigger broader associations - Require more contextual processing - Weaker memory encoding ### Embodied Cognition (USC Research, 2022) First-time demonstration that figurative language requires motor regions: - "Grasp the concept" activates hand-movement areas - Sensory metaphors activate corresponding sensory cortex - Creates deeper processing and stronger memory traces ### Sensory Language Activation | Language Type | Brain Region Activated | |--------------|------------------------| | Action verbs | Motor cortex | | Texture words | Somatosensory cortex | | Color/visual words | Occipital regions | | Sound words | Auditory cortex | **Example transformation:** ``` Abstract: "The code was problematic" Concrete: "The code sprawled like tangled Christmas lights—one pull and everything breaks" ``` The concrete version activates visual and tactile regions, creating richer memory encoding. ## Persuasion Principles ### Cialdini's Seven Principles Applied to Writing 1. **Reciprocity**: Give value first (insights, stories, emotion) - "Here's what I learned so you don't have to..." 2. **Scarcity**: Emphasize uniqueness or time sensitivity - "The one technique no one talks about..." 3. **Authority**: Cite credible sources and expertise - "According to Stanford's 10-year study..." 4. **Consistency**: Align with reader's existing values - "As engineers, we value clean code..." 5. **Liking**: Create identification through relatable voice - "Like you, I used to think..." 6. **Social Proof**: Show others' engagement/acceptance - "12,000 developers have already switched..." 7. **Unity**: Build "we" identity with readers - "We all know the pain of..." ### The Power of "You" **Nature Communications study** (25,679 peer review instances): Using "you" vs third-person resulted in: - Fewer follow-up questions - Shorter response times - More positive feedback **Mechanism**: Second-person pronouns: - Create personal, engaging conversation - Enhance perspective-taking - Increase experiential aspects of reading - Show early processing advantage in eye-tracking ## The Curiosity Gap ### Loewenstein's Framework (Carnegie Mellon) **Core concept**: Curiosity arises from perception of a gap in knowledge - Creates cognitive tension (mild discomfort) - Motivates information-seeking to resolve tension - Functions like physiological homeostasis **Requirements for effective curiosity gap:** - **Specific enough** to create focused curiosity - **Bridgeable** (reader believes they can learn the answer) - **Relevant** to reader's existing knowledge/interests ### The Zeigarnik Effect Uncompleted tasks create persistent cognitive tension: - Unresolved story threads maintain engagement - Cliffhangers leverage this pressure - Resolution provides satisfaction **Application**: Open loops early, close them strategically. ### Curiosity Gap Examples **Weak** (too vague): "I learned some interesting things about productivity" **Strong** (specific gap): "The CEO asked me one question that changed how I think about time" **Weak** (no gap): "Here are 5 tips for better code reviews" **Strong** (creates tension): "The 5th tip on this list got me fired. It also tripled my salary." ## Story Arc and Engagement ### Why Three-Act Structure Works **Neuroscience basis:** **Act 1 (Setup)**: Establishes predictions and expectations - Dopamine anticipation begins - Reader creates mental model **Act 2 (Confrontation)**: Violates predictions - Tension creates cortisol response - Prediction errors enhance encoding **Act 3 (Resolution)**: Delivers payoff - Oxytocin release if empathy achieved - Satisfies prediction-reward circuits ### Zak's Research on Attention - Attention waxes/wanes with environmental scanning - Peak attentional response at climax - Oxytocin response lags ~30 seconds behind attention spike - Stories need rising tension to maintain engagement ## Practical Application ### For Maximum Memory Retention 1. **Use specific details**: "The jagged scar above his left eye" vs "He had a scar" 2. **Create contrast**: Higher cognitive contrast = 15% better recall 3. **Build predictions then violate them**: Prediction errors create distinctive memories 4. **Front-load and back-load importance**: Serial position effect ### For Emotional Engagement 1. **Follow dramatic arc**: Rising tension → climax → resolution 2. **Enable character identification**: Access to inner states, motivations 3. **Use second-person "you"**: Creates personal connection 4. **Employ sensory language**: Activates multiple brain regions ### For Persuasive Impact 1. **Leverage social proof**: Show others' engagement 2. **Create reciprocity**: Give value before asking 3. **Build consistency**: Align with reader's existing values 4. **Establish authority**: Cite credible sources ### For Curiosity and Engagement 1. **Open with specific question**: Not vague, not answered immediately 2. **Create information gaps**: Reveal partial information 3. **Promise specific value**: "You'll learn exactly how to..." 4. **Delay key revelations**: Strategic placement of payoffs -
revision-frameworks.md 13.2 KB
# Revision Frameworks and Editing Science Research-backed processes for transforming drafts into impactful content. ## Contents - The Four-Level Editing System - Revision Strategy Research - The Conciseness Pass - Active Voice Conversion - Before/After Case Studies - Self-Editing Techniques - Common Revision Mistakes ## The Four-Level Editing System ### Overview Professional editors work through four distinct levels, never mixing concerns: | Level | Focus | Time Investment | |-------|-------|-----------------| | 1. Developmental | Structure, content, argument | 30-50% | | 2. Line | Style, clarity, flow | 25-35% | | 3. Copy | Grammar, consistency, facts | 20-30% | | 4. Proofreading | Typos, formatting | 10-15% | **Critical principle**: Work through levels sequentially. Fixing typos before addressing structure wastes time. ### Level 1: Developmental Editing **Focus**: Big-picture organization, narrative flow, argument structure **Questions to ask:** - What is the core message? (Write it in one sentence) - Does every section advance this message? - Is information in logical order? - Are there gaps in logic or evidence? **Technique**: Reverse outline - After drafting, outline what you wrote - Each paragraph = one bullet - Gaps and redundancies become visible ### Level 2: Line Editing **Focus**: Sentence-level improvements, paragraph flow, voice consistency **Questions to ask:** - Is this the clearest way to say this? - Can I say this in fewer words? - Does each paragraph have one clear focus? - Are transitions smooth? **Technique**: Read aloud - Unclear passages trip your tongue - Run-on sentences make you gasp for breath - Awkward phrasing becomes obvious ### Level 3: Copyediting **Focus**: Grammar, punctuation, style guide adherence, fact-checking **Questions to ask:** - Is this grammatically correct? - Is it consistent with prior usage? - Are facts and citations accurate? **Technique**: Separate passes for different concerns - One pass for punctuation - One pass for consistency - One pass for facts ### Level 4: Proofreading **Focus**: Typos, formatting, layout issues **Questions to ask:** - Are there any remaining errors? - Is formatting consistent? - Do all links work? **Technique**: Read backwards - Forces focus on individual words - Prevents brain from "filling in" expected text - Catches typos the eye normally skips ## Revision Strategy Research ### Graham & Perin Meta-Analysis (2007) Analysis of 123 studies with 154 effect sizes: | Intervention | Effect Size | |--------------|-------------| | Strategy instruction | 0.82 (highest) | | Sentence combining | 0.50 | | Process writing | 0.32 | | Grammar instruction | -0.32 (negative) | **Key insight**: Teaching explicit revision strategies has nearly triple the impact of teaching grammar rules. ### What "Strategy Instruction" Means The most effective approach combines: 1. **Cognitive strategies**: Planning, organizing, self-regulation 2. **Metacognitive strategies**: Self-assessment, reflection 3. **Procedural knowledge**: Specific techniques to apply **Implication**: Having a revision process matters more than knowing grammar rules. ### Timing Research Studies show separating drafting from editing improves quality: - Self-assessment before and after revision improves both self-efficacy and writing - 24-hour gap between drafting and editing recommended (cognitive refresh) - "Kill your darlings" easier with time distance ## The Conciseness Pass ### Scott Hotaling's Framework (Limnology and Oceanography Letters, 2020) Three types of filler that reduce conciseness: **1. Qualifiers (adverbs)** - Examples: quickly, extremely, frequently, very, really - Impact: Often add zero information - Fix: Remove entirely in most cases **2. Prepositional phrase chains** - Examples: "in this case," "among other things," "on the other hand" - Impact: Make sentences jumbled and unclear - Fix: Replace multi-word phrases with single words **3. Overused transitions** - Examples: however, meanwhile, thus, furthermore - Impact: Create verbal clutter when overused - Fix: Remove extraneous transitions, combine sentences ### Common Wordy Phrases | Wordy | Concise | Words Saved | |-------|---------|-------------| | due to the fact that | because | 4 | | in order to | to | 2 | | at this point in time | now | 4 | | in the event that | if | 3 | | with regard to | about | 2 | | for the purpose of | to | 3 | | in spite of the fact that | although | 5 | | it is important to note that | (delete entirely) | 6 | | the reason why is that | because | 3 | | until such time as | until | 3 | ### Unnecessary Lead-Ins | Cut This | Keep This | |----------|-----------| | "It is worth noting that the data shows..." | "The data shows..." | | "In terms of the findings, we see that..." | "We found..." | | "As far as the analysis is concerned..." | "The analysis..." | | "With respect to the issue of..." | (State the issue directly) | ### Word Simplification | Complex | Simple | Syllables Saved | |---------|--------|-----------------| | utilize | use | 2 | | commence | start | 1 | | terminate | end | 2 | | demonstrate | show | 2 | | facilitate | help | 3 | | subsequently | later | 2 | | approximately | about | 3 | | endeavor | try | 2 | | ascertain | find out | 1 | | implement | do, use | 2 | ### Compound Effect Small edits compound across documents: - 8,000-word document - 50 phrase simplifications (average 3 words each) - 150 words saved - 10-30% length reduction possible ## Active Voice Conversion ### Identification Passive voice pattern: form of "to be" + past participle | Passive Indicator | Example | |-------------------|---------| | is/was + past participle | "was written" | | are/were + past participle | "were found" | | has/have been + past participle | "has been completed" | | will be + past participle | "will be reviewed" | ### Conversion Process 1. Identify the true actor (who/what performs the action) 2. Make the actor the subject 3. Use active verb form **Examples:** | Passive | Active | |---------|--------| | The report was written by the team | The team wrote the report | | Errors were found in the code | We found errors in the code | | The meeting was scheduled for 3pm | I scheduled the meeting for 3pm | | A decision was made to proceed | The board decided to proceed | | The feature has been implemented | We implemented the feature | | Concerns were raised about costs | Stakeholders raised concerns about costs | ### When to Keep Passive Keep passive voice only when: - **Actor unknown**: "The window was broken" (no one knows by whom) - **Actor irrelevant**: "The samples were collected" (focus on samples, not collector) - **Object emphasis**: "Three bugs were fixed" (emphasis on bugs) - **Hedging appropriate**: "Mistakes were made" (deliberately vague) **Default**: Convert to active unless specific reason to keep passive. ## Before/After Case Studies ### Case Study 1: Legal Court Form **Original** (complex): - Average comprehension: 61% - Sentence length: 28 words average **Revised** (plain language): - Average comprehension: 81% (+33%) - Sentence length: 16 words average - Length: 40% shorter **Changes made:** - Sentence length reduced from 28 to 16 words - Legal jargon removed: "hereinafter," "aforementioned," "pursuant to" - Active voice throughout - Clear headings and white space - Steps listed numerically ### Case Study 2: Judicial Opinion **Original:** > The plaintiff commenced an action in this Court seeking declaratory relief with respect to the issue of whether or not the defendant insurance company has an obligation under the applicable policy provisions to provide coverage for the injuries sustained by the plaintiff in the accident which is the subject matter of this litigation. (51 words, one sentence) **Revised:** > Robert Wills was injured when someone fired shots toward his car, causing him to swerve into a tree. He filed a declaratory-judgment action to determine whether State Farm had to pay him uninsured-motorist benefits. (35 words, two sentences) **Results:** - 61% of lawyers preferred revised version - Rated 7/10 vs 6/10 ### Case Study 3: Technical Documentation **Before:** > In order to facilitate the implementation of the authentication functionality, it will be necessary for developers to utilize the OAuth2 library which has been provided in the dependencies folder, ensuring that the appropriate configuration parameters have been set in accordance with the specifications outlined in the configuration documentation. (53 words) **After:** > To add authentication, use the OAuth2 library in the dependencies folder. Set the configuration parameters as described in config.md. (20 words) **Improvement:** - 62% fewer words - Same information - Clearer action steps ### Case Study 4: Email Communication **Before:** > I am writing to follow up with you regarding the matter we discussed in our previous meeting concerning the upcoming project deliverables. As we discussed, it would be beneficial for us to schedule a time to meet in order to review the current status of the project and to discuss any potential issues that may need to be addressed prior to the deadline. (68 words) **After:** > Can we meet this week to review the project status before the deadline? I want to address any issues early. (20 words) **Improvement:** - 70% fewer words - Clear action requested - Specific timeline ## Self-Editing Techniques ### Technique 1: The "So What?" Test **Application**: After each paragraph, ask "So what?" If you can't answer clearly, the paragraph needs revision. **Example:** > "The system uses a microservices architecture." So what? > "The system uses a microservices architecture, so you can update individual components without redeploying everything." ### Technique 2: One Idea Per Sentence **Application**: If sentence contains "and," "but," or "however," consider splitting. **Before:** > "The API is fast and reliable but requires authentication and uses rate limiting." **After:** > "The API is fast and reliable. It requires authentication and uses rate limiting." ### Technique 3: Front-Load Subject and Verb **Application**: First 7-8 words should contain subject and main verb. **Before:** > "In order to understand the implications of the proposed changes to the system architecture, developers need to review the documentation." **After:** > "Developers need to review the documentation to understand the proposed changes." ### Technique 4: The Grandmother Test **Application**: Would a non-expert understand the main point? If not, simplify until they would. ### Technique 5: The Cut Test **Application**: For each sentence, ask "Can I remove this without losing meaning?" If yes, remove it. ### Technique 6: Kill Your Darlings **Application**: Identify your favorite phrases. Evaluate them critically. Writers overvalue their clever phrasing (overconfidence bias). Favorite phrases often serve the writer's ego, not the reader's understanding. ### Technique 7: Convert Nominalizations **Application**: Change noun phrases back to verbs. | Nominalization | Verb Form | |----------------|-----------| | made an investigation into | investigated | | reached a conclusion about | concluded | | gave consideration to | considered | | performed an analysis of | analyzed | | made a decision to | decided to | ### Technique 8: The 24-Hour Rule **Application**: Wait 24 hours between drafting and editing. Cognitive refresh reveals: - Unclear passages you thought were clear - Redundancies you missed - Missing transitions you assumed were there ## Common Revision Mistakes ### Mistake 1: Editing While Drafting **Problem**: Interrupts creative flow, wastes time on text you'll delete **Fix**: Draft first, edit later (separate sessions) ### Mistake 2: Starting with Grammar **Problem**: You'll fix sentences you later delete **Fix**: Work developmental → line → copy → proof ### Mistake 3: Over-Reliance on Tools **Problem**: Tools don't understand context or meaning **Fix**: Use tools for detection, not decision-making ### Mistake 4: Accepting All Suggestions **Problem**: Not every "issue" is actually a problem **Fix**: Evaluate each suggestion against context and purpose ### Mistake 5: Ignoring Reader Feedback **Problem**: Authors can't see their own blind spots **Fix**: Seek external feedback; it correlates with improvement ### Mistake 6: Single-Pass Revision **Problem**: Different issues require different attention **Fix**: Multiple passes, each with focused purpose ## Quantified Improvement Targets **Based on research synthesis, effective revision should achieve:** | Metric | Target | |--------|--------| | Word reduction | 10-30% from first to final draft | | Average sentence length | 15-20 words | | Maximum sentence length | 25 words | | Passive voice | <10% of sentences | | Adverbs (qualifiers) | Reduce by 50-70% | | Multi-syllable words | Reduce by 20-30% where possible | | Readability (Flesch) | 60-70 for general audience | ## Revision Workflow Summary ### Phase 1: Macro (30-40% of time) - Structure and organization - Core message clarity - Information hierarchy ### Phase 2: Clarity (25-35% of time) - Sentence simplification - Active voice conversion - Jargon elimination ### Phase 3: Conciseness (15-20% of time) - Word elimination - Phrase simplification - Redundancy removal ### Phase 4: Polish (10-15% of time) - Grammar and punctuation - Consistency check - Final proofreading -
structure-patterns.md 10.9 KB
# Content Structure and Formatting Patterns Research-backed principles for how to organize and present content. ## Contents - Eye-Tracking and Reading Patterns - The Inverted Pyramid - White Space Science - Headings and Subheadings - Lists vs Paragraphs - Chunking and Cognitive Load - Mobile vs Desktop Behavior - Scanability Optimization ## Eye-Tracking and Reading Patterns ### The F-Pattern (Nielsen Norman Group, 2006-2017) **Study details**: 232 users across thousands of web pages, tracked over 11 years **Three movements of the F-pattern:** 1. **Horizontal movement** across upper content (F's top bar) 2. **Second horizontal movement** lower down, typically shorter (F's lower bar) 3. **Vertical scan** down the left side (F's stem) **Key findings:** - First two paragraphs receive most attention - Left-aligned text gets 69% more visual attention - Content on right side often ignored - Users rarely read word-for-word; scanning is default ### Four Main Scanning Patterns (2019 Update) 1. **F-Pattern**: Traditional horizontal-vertical scanning (least effective for content absorption) 2. **Spotted Pattern**: Skipping to visually distinct elements - Users focus on: links, bold text, bullets, numbers - Effectiveness depends on highlighting key terms 3. **Layer-Cake Pattern**: Scanning headings only (highly effective) - Readers scan headings until finding relevant section - Creates horizontal stripe pattern in heat maps - "Aside from reading every word, the most effective scanning pattern" 4. **Commitment Pattern**: Traditional reading (rare, 10-20% of users) - Occurs when users highly motivated - Most comprehensive but time-consuming ### Design Implications - **Most users read very little**: Assume scanning - **Support scanning through**: - Meaningful subheadings - Bulleted lists - Visual styling for keywords - Chunked sections - **79% of web visitors skim** rather than read every word - **Average time on page: 15 seconds** ## The Inverted Pyramid ### Origin and Validation Journalism best practice validated by Nielsen Norman Group (2018). **Core principle**: Most important information first, followed by supporting details in descending order of importance. ### Benefits Measured - **Improved comprehension**: Users form mental models faster - **Decreased interaction cost**: Main point understood without deep reading - **Encourages scrolling**: 71% more likely to scroll when engaged by opening - **Supports skimmers**: Users can stop at any point with understanding ### Structure | Section | Reader Reach | Content | |---------|-------------|---------| | First paragraph | 100% | The conclusion/main point | | Second paragraph | 50-80% | Critical supporting details | | Subsequent | 20% | Decreasing importance | ### Effectiveness Data - 20% higher comprehension scores - 35% faster task completion - 40% reduction in bounce rate ### Application ``` Traditional (avoid): Background → Context → Details → Conclusion Inverted Pyramid (prefer): Conclusion → Key Evidence → Supporting Details → Background ``` ## White Space Science ### Research Evidence **Key study** (Hurley Write, 2020): White space in margins improves comprehension by approximately 20%. ### Psychological Impact - Reduces visual clutter - Decreases cognitive load by 18% - Improves focus on key elements - Creates perception of quality and professionalism ### Types of White Space **Macro white space**: Large gaps between major elements - Increases comprehension by 20% - Reduces eye strain - Guides visual hierarchy **Micro white space**: Small gaps (line spacing, letter spacing) - Improves readability by 12% - Enhances text legibility - Reduces reading fatigue ### WCAG Accessibility Requirements | Element | Requirement | |---------|-------------| | Line height | 1.5em (1.5× font size) | | Paragraph spacing | 2em | | Word spacing | 0.16em minimum | | Letter spacing | 0.12em minimum | ### Practical Guidelines - Line height: 1.4-1.6 for body text - Paragraph spacing: At least 1.5× line height - Section spacing: 2-3× paragraph spacing - Margins: Generous—white space is not wasted space ## Headings and Subheadings ### Eye-Tracking Evidence **Research findings** (Hyöna & Lorch, 2004-2006): - Headings receive disproportionate attention - Users spend 2-3x longer on headings than body text - Layer-cake scanning: Many users read headings only ### Meta-Analysis on Text Structure **Bogaerds-Hazenberg et al. (2021):** - Text structure instruction improves comprehension by 0.35 standard deviations - Descriptive headings improve recall by 28% - Hierarchical structure reduces cognitive load ### Best Practices **Effective headings are:** 1. **Descriptive**: Communicate content, not clever wordplay 2. **Front-loaded**: Key words at beginning 3. **Hierarchical**: Clear H1 → H2 → H3 structure 4. **Scannable**: Stand alone without context 5. **Specific**: 6-8 words optimal **Heading frequency:** - Every 3-4 paragraphs for long-form content - Every 300-500 words as rough guide ### Impact Data Sites with effective heading hierarchies show: - 47% improvement in task completion - 32% faster information retrieval - 40% better user satisfaction ## Lists vs Paragraphs ### When Lists Win **Research findings (multiple studies):** - 3x better recall of individual items in lists vs paragraphs - Lists highlight key points more effectively - Processing advantage for item-specific information - 40% faster information retrieval **Lists excel for:** - Enumerating features or steps - Presenting options or choices - Highlighting key takeaways - Mobile interfaces (critical for scanability) ### When Paragraphs Work Better **Research caveats:** - **Heterogeneous content**: Mixed information types work better in paragraphs - **Context retention**: Lists can decrease recall of surrounding content by 15% - **Narrative flow**: Complex arguments need paragraph structure - **Relationships**: When items are interconnected ### Optimal List Implementation **Best practices from studies:** - Lead-in sentence to frame the list - Parallel structure (consistent grammar) - Appropriate punctuation based on content - One level deep maximum (nested lists -23% comprehension) - 2 sentences maximum per bullet point **Nielsen Norman Guideline**: Use lists when you have 3+ related items; use paragraphs for narrative or complex relationships. ## Chunking and Cognitive Load ### The Science **George Miller (1956)**: Working memory holds 5-9 "chunks" of information. **Modern application** (Nielsen Norman Group, 2016): - Breaking content into chunks improves processing - Chunks should represent meaningful units - Optimal chunk size: 3-5 related items ### Chunking Strategies 1. **Paragraph breaks**: Visual breathing room 2. **Subheadings**: Topic boundaries 3. **Lists**: Related items grouped 4. **Visual separators**: Borders, spacing, color blocks 5. **Progressive disclosure**: Reveal complexity gradually ### Impact Data | Metric | Improvement | |--------|-------------| | Comprehension | +24% | | Perceived difficulty | -31% | | User confidence | +28% | | Cognitive load | Significantly reduced | ### Practical Implementation **For articles/blog posts:** - Break every 3-4 paragraphs with heading - Limit paragraphs to 3-5 sentences - Use lists for enumeration - Add visual breaks between major sections **For documentation:** - One concept per section - Code examples as visual chunks - Progressive complexity - Clear section boundaries ## Mobile vs Desktop Behavior ### Behavioral Differences | Factor | Mobile | Desktop | |--------|--------|---------| | Session length | 40-60% shorter | Baseline | | Peak times | Morning (6-9 AM), evening | Work hours (9 AM-6 PM) | | Bounce rate | +32% for poor optimization | Baseline | | Scrolling | 50% more | Less | | Content preference | Light, quick updates | Deeper research | ### Reading Pattern Differences **Mobile behavior:** - More rapid scanning - Thumb-driven scrolling - Higher abandonment on dense text - Preference for bite-sized content **Desktop behavior:** - Deeper reading for research - Tolerance for longer content - Mouse-driven precision scanning ### Mobile-Specific Optimization **Critical adjustments:** 1. Shorter paragraphs: 3-4 lines maximum 2. More white space: 1.5-2x desktop spacing 3. Larger tap targets: 44×44 pixels minimum 4. Stronger hierarchy: Bigger heading distinctions 5. Front-loaded content: Even more critical **Research finding**: Mobile users show 60% better comprehension when content is specifically optimized for mobile. ## Scanability Optimization ### Why Scanability Matters **User behavior data:** - Users read 20-28% of words on a page - Average time on page: 15 seconds - Decision to stay/leave: First 10 seconds - 80% of users scan; 20% read thoroughly ### Elements That Enhance Scanability **Ranked by impact (eye-tracking studies):** | Element | Scanner Engagement | |---------|-------------------| | Headings/Subheadings | 89% | | Bulleted lists | 70% | | Bold/emphasized text | 65% | | Short paragraphs (first lines) | 58% | | Images with captions | 45% | | Numbers and data | 42% | | Pull quotes | 38% | | White space | 35% | ### The Scanability Formula **Optimal content structure:** - **Headings**: Every 3-4 paragraphs - **Paragraph length**: 3-5 sentences maximum - **Sentence length**: 15-20 words average - **Lists**: For 3+ related items - **Bold keywords**: 2-3 per section - **Line length**: 50-75 characters - **White space**: 40-60% of page ## Gestalt Principles for Content ### Key Principles **1. Proximity**: Related items should be close together - Reduces cognitive effort by 19% - Creates implicit groupings - Users process grouped items as single units **2. Similarity**: Similar items perceived as related - Consistent formatting creates patterns - Users scan 23% faster - Reduces learning curve **3. Continuity**: Eyes follow continuous lines/patterns - Guides reading flow - Creates visual hierarchy - Improves navigation by 35% **4. Figure/Ground**: Content vs background separation - Essential for readability - 4.5:1 contrast ratio minimum (WCAG AA) - Proper contrast reduces strain ### Application to Content - Use proximity to group related paragraphs - Apply similarity in heading styles consistently - Create continuity with alignment and spacing - Ensure figure/ground with adequate contrast ## Practical Checklist ### Before Publishing **Structure:** - [ ] Inverted pyramid: Key point in first paragraph - [ ] Headings every 3-4 paragraphs - [ ] Paragraphs 3-5 sentences maximum - [ ] Lists for 3+ related items **Formatting:** - [ ] Line length 50-75 characters - [ ] Adequate white space (line height 1.5+) - [ ] Bold for 2-3 key terms per section - [ ] Consistent heading hierarchy **Scanability:** - [ ] First 10 seconds capture attention - [ ] Key points visible without scrolling - [ ] Visual hierarchy guides the eye - [ ] Content works without reading every word **Mobile:** - [ ] Paragraphs 3-4 lines on mobile - [ ] Tap targets adequate (44×44px) - [ ] Front-loaded content - [ ] Tested on actual mobile device
-
-
LICENSE.txt 8.9 KB
Apache License Version 2.0, January 2004 https://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS -
SKILL.md 10.7 KB
--- name: impactful-writing description: 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. metadata: version: "0.1.4" categories: "creative, knowledge" topics: "writing, editing, storytelling, clarity, copywriting" openclaw: homepage: https://github.com/tenequm/skills/tree/main/skills/impactful-writing emoji: "✍️" --- # Impactful Writing ## Overview 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. ## When to Use This Skill - Writing or editing Twitter/X posts, threads, or social content - Creating blog posts, Medium articles, or long-form content - Drafting documentation, README files, or technical writing - Composing emails, Slack messages, or professional communication - Writing GitHub comments, PR descriptions, or code reviews - Creating update messages, announcements, or change logs - Editing any existing content for clarity and impact ## Universal Writing Principles These evidence-based principles work across all platforms and contexts. ### 1. Clarity Through Simplicity **Sentence length determines comprehension:** - 14 words: 90%+ reader comprehension - 25 words: Difficulty begins - 43 words: <10% comprehension **Target: 15-20 words average, 25 words maximum per sentence.** **Word choice matters:** - Simple words process 76% faster than jargon - Active voice processes 15-20% faster than passive - Concrete beats abstract (activates sensory brain regions) ### 2. Structure for Scanning **79% of readers scan rather than read.** Design for this reality: - Front-load key information (inverted pyramid) - Use descriptive headings every 3-4 paragraphs - Keep paragraphs to 3-5 sentences maximum - Use bullet points for 3+ related items - Optimal line length: 50-75 characters ### 3. Emotional Resonance **Stories trigger oxytocin release**, enabling empathy and memory formation: - Open with a hook (question, surprising fact, brief story) - Use sensory, concrete language - Create curiosity gaps (specific questions readers want answered) - Close with memorable takeaways (recency effect) ### 4. Specificity Over Abstraction Specific details outperform vague statements: - "45% increase" beats "significant growth" - "in 5 minutes" beats "quickly" - "10 ways" beats "several ways" - Concrete examples beat abstract explanations ## Quick Start Workflow ### Writing New Content 1. **Define the core message** in one sentence 2. **Open with a hook** (question, fact, or story) 3. **Structure with headings** for scannability 4. **Use short sentences** (15-20 words average) 5. **Close with clear takeaway** or call-to-action ### Editing Existing Content 1. **Read aloud** to identify awkward passages 2. **Cut word count** by 10-30% without losing meaning 3. **Convert passive to active** voice 4. **Replace jargon** with simple words 5. **Add structure** (headings, bullets, white space) ## Platform-Specific Guidance ### Twitter/X Posts - **Optimal length**: 71-100 characters for engagement - **Hook in first line**: Must capture in 3 seconds - **Use numbers**: "10 lessons" outperforms "lessons learned" - **Thread structure**: Each tweet must stand alone AND connect 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:" ``` ### Blog Posts / Articles - **Optimal reading time**: 7-10 minutes - **Headings**: Every 300-500 words - **First paragraph**: Must deliver the promise - **Conclusion**: Summarize key points, provide clear next step ### Technical Documentation - **Lead with the goal**: What will the reader accomplish? - **Show, don't tell**: Working code examples beat explanations - **Progressive disclosure**: Basic → Advanced - **Consistent terminology**: One term per concept ### Professional Communication (Email/Slack) - **Subject lines**: Specific over clever ("Q4 Report Draft" > "Quick update") - **One topic per message**: Increases response rate - **Front-load action items**: Don't bury the ask - **Keep to half-page maximum**: Longer = lower read rate ### GitHub Comments / PR Descriptions - **Start with context**: What problem does this solve? - **Use bullet lists**: For changes, decisions, trade-offs - **Include "why"**: Reasoning > description - **Be direct but kind**: Critique code, not people ## The Revision Checklist 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 ``` ## Word Reduction Patterns 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 | ## Hook Patterns That Work ### Question Hook Opens with a question the reader wants answered: ``` "What if everything you knew about productivity was wrong?" ``` ### Statistic Hook 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." ``` ### Story Hook 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." ``` ### Declarative Hook Opens with a bold statement: ``` "Most advice about writing is wrong. Here's what actually works." ``` ### Contradiction Hook Challenges an assumption: ``` "The best writers don't write more. They delete more." ``` ## Memory and Impact Principles Content that sticks follows these patterns: ### Serial Position Effect - **First items**: ~70% recall (primacy) - **Last items**: ~60% recall (recency) - **Middle items**: ~40% recall **Implication**: Put most important points first and last. ### Prediction Errors 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." ``` ### Sensory Language Activates multiple brain regions: ``` Before: "The code was messy." After: "The code sprawled like tangled Christmas lights - one pull and everything breaks." ``` ## Common Anti-Patterns ### Over-Explaining **Problem**: Explaining what readers already know **Fix**: Assume intelligence, provide only new information ### Buried Lede **Problem**: Key point in paragraph 3 **Fix**: Move conclusion to opening, support with details ### Wall of Text **Problem**: Dense paragraphs without visual breaks **Fix**: Add headings, bullets, white space ### Passive Avoidance **Problem**: "Mistakes were made" (who made them?) **Fix**: "The team missed the deadline" (clear ownership) ### Jargon Cascade **Problem**: "We synergized cross-functional paradigms" **Fix**: "We got the teams to work together" ## Proven Content Frameworks ### AIDA (Attention → Interest → Desire → Action) 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." ``` ### PAS (Problem → Agitate → Solution) 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." ``` ### BAB (Before → After → Bridge) 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." ``` ### 1-2-3 Structure 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 ``` ## Detailed References For deeper guidance on specific topics: - **[references/clarity-science.md](references/clarity-science.md)**: Research on readability, cognitive load, and plain language with specific metrics - **[references/emotional-impact.md](references/emotional-impact.md)**: Neuroscience of storytelling, memory, and persuasion - **[references/structure-patterns.md](references/structure-patterns.md)**: Eye-tracking research, scanning patterns, and formatting - **[references/revision-frameworks.md](references/revision-frameworks.md)**: Professional editing processes and before/after examples ## Quick Reference: The CLEAR Framework **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? ## Validation: Content Quality Check After writing, verify: 1. **Core message test**: Can you state it in one sentence? 2. **So what test**: After each paragraph, can you answer "so what"? 3. **Grandmother test**: Would a non-expert understand the main point? 4. **Action test**: Does the reader know what to do next? 5. **Cut test**: Can you remove any sentence without losing meaning? If any test fails, revise that section.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.