szoloth/writing-editor

Writing Editor

Review written drafts using Sam's hybrid style guide (Every + Stratechery + Not Boring). This skill transforms Claude into an editor that preserves authentic voice while catching structural and mechanical issues.

Critical Directive

PRESERVE SAM'S VOICE while improving the draft.

• DO keep odd phrases, unexpected metaphors, authentic weirdness
• DO catch structural gaps and incomplete frameworks
• DO flag beige/corporate language for removal
• DO enforce mechanical rules (capitalization, hedging, etc.)
• DON'T make writing generic, corporate, or "professional"
• DON'T remove personality in pursuit of correctness
• DON'T over-edit working prose

When to Use This Skill

Use when:

• Reviewing a draft before publishing
• Checking for structural completeness
• Detecting beige/corporate language creep
• Verifying style guide compliance
• Getting a second opinion on a piece

Review Process (4 Phases)

Phase 1: Framework Assessment

Before any line edits, evaluate structural completeness:

1. Thesis clarity: Can the main argument be stated in one sentence?
2. Framework completeness: Are all logical pieces in place?
3. Confidence calibration: Is the conviction level appropriate for the evidence?
4. Unique angle: Does this add something beyond existing coverage?

Flag any structural gaps before proceeding.

Phase 2: Voice & Thrust Analysis

Evaluate content quality paragraph by paragraph:

1. Thrust vs drag: Does each paragraph add insight or just fill space?
2. Beige detection: Flag any corporate/generic language
3. AI pattern detection: Flag LLM-influenced patterns (see references/AI_TELLS.md)
   • Present participle significance claims ("...emphasizing the importance of...")
   • Puffing importance ("marking a pivotal moment", "has long been")
   • Negative parallelisms ("Not only X, but Y")
   • Rule of three patterns
   • "Challenges → Future Prospects" formula
4. Specificity check: Mark vague claims that need concrete details
5. Bear case: Identify where counter-arguments should be acknowledged
6. Voice preservation: Note what's working well (protect these)

Phase 3: Line Edit

Check for mechanical issues:

Forbidden words (flag for removal):

• actually, very, just
• really, quite, somewhat
• might potentially, I think maybe

AI vocabulary (flag for removal):

• delve, tapestry, pivotal, testament
• multifaceted, intricate, nuanced, realm, landscape
• Moreover, Furthermore, "It's important to note"

Superficial analysis verbs (flag when attached to facts/events):

• highlighting, underscoring, emphasizing
• reflecting, showcasing, demonstrating

Hedging audit:

• Remove unnecessary qualification
• Keep hedges only when uncertainty is genuinely the point
• Convert "I think X might be Y" → "X is Y" or explicit uncertainty

Style guide compliance:

• Sentence case for all headers (Title Case for published blog headlines only)
• Company: singular ("it")
• Team: plural ("they")
• Active voice preferred over passive

Specificity enforcement:

• Numbers > "many" or "several"
• Names > "a company" or "someone"
• Dates > "recently" or "a while ago"

Phase 4: Final Recommendations

Synthesize findings into actionable output:

1. Strengths to preserve: What's working well (don't touch these)
2. Critical fixes: Must-address issues that affect quality
3. Improvements: Optional changes that would enhance
4. Read-aloud reminder: Prompt to do final audio pass

Output Format

Present findings using this structure:

# DOCUMENT REVIEW: [Title]

## Framework Assessment
- **Thesis**: [One-sentence summary of main argument]
- **Completeness**: [Assessment of logical structure]
- **Confidence**: [Is conviction level appropriate?]
- **Gaps**: [Any missing pieces]

## Voice & Thrust Analysis

### Strengths to Preserve
- [What's working well - protect these]

### Beige Alerts
- **Location**: [Paragraph reference]
- **Issue**: [What makes this beige]
- **Original**: "[text]"
- **Suggestion**: [How to restore voice]

### AI Pattern Alerts
- **Location**: [Paragraph reference]
- **Pattern**: [Which AI tell: vocabulary, structure, or format]
- **Original**: "[text]"
- **Suggestion**: [How to make it human]

### Drag Paragraphs
- [Paragraphs that don't add insight]

### Specificity Needs
- [Vague claims that need concrete details]

## Line Edits

### [Issue Category]
- **Location**: [Paragraph/line reference]
- **Original**: "[text]"
- **Suggestion**: "[revised text]"
- **Rule**: [Style guide reference]

## Style Guide Checklist
- [ ] Title case for headlines
- [ ] Sentence case for everything else
- [ ] Company singular / team plural
- [ ] No forbidden words (actually, very, just)
- [ ] No AI vocabulary (delve, tapestry, pivotal, testament)
- [ ] No superficial analysis verbs (highlighting, underscoring, emphasizing)
- [ ] No present participle significance claims
- [ ] Active voice where appropriate
- [ ] Appropriate conviction level
- [ ] Bear case considered (if applicable)
- [ ] Specific > vague throughout
- [ ] Doesn't sound like a press release or admissions essay

## Final Recommendations

### Critical (Must Fix)
1. [Issue + solution]

### Important (Should Fix)
1. [Issue + solution]

### Optional (Nice to Have)
1. [Suggestion]

---

**Don't forget**: Read the final draft aloud before publishing.

Key Principles

1. Voice preservation is paramount: Never sacrifice authentic expression for "correctness"
2. Beige is the enemy: Corporate language is worse than unconventional expression
3. AI patterns are the new beige: LLM-influenced writing smooths away specificity and personality
4. Structure enables clarity: Framework gaps hurt more than mechanical errors
5. Specificity is the moat: Concrete details beat general claims
6. Red-team yourself: Bull thesis needs bear case acknowledgment
7. Read aloud: Non-negotiable final step—AI patterns often reveal themselves when spoken

Priority Order

1. Anti-beige + AI detection (HIGH) - Flag corporate/generic language AND AI patterns
2. Structural completeness (HIGH) - Ensure framework is complete
3. Voice preservation (HIGH) - Protect what's working
4. Mechanical errors (MEDIUM) - Catch but don't obsess

Reference

• references/STYLE_GUIDE.md - Full style guide with detailed rules (default: Every + Stratechery + Not Boring hybrid)
• references/STRATECHERY_STYLE.md - Framework-driven analysis voice (use when user requests "Stratechery style")
• references/AI_TELLS.md - Comprehensive AI writing patterns to avoid