CONTENT-WRITING SuperSkill

Триггеры: "контент", "статья", "гуманизация", "человеческий стиль", "AI writing", "текст", "документация" Атомов: 38

WHEN TO USE

• Writing/editing text for humans → apply humanization rules
• AI-generated text review → run anti-AI checklist
• Product descriptions, landing copy → use templates
• Any output that feels "too clean" → add soul
• Documentation → keep factual, skip humanization

KEY ACTIONS

Step 1: Write the content

Draft normally, focusing on substance and accuracy.

Step 2: Anti-AI pass (remove these patterns)

Kill list -- words to eliminate: delve, crucial, pivotal, landscape, tapestry, multifaceted, stands as a testament, underscores the importance, indelible mark, setting the stage, evolving landscape, it's important to note, it's worth noting

Kill list -- structures to eliminate:

• "It's not just X; it's Y and Z" (negative parallelism)
• "Moreover, furthermore, additionally, consequently" (excessive conjunctives)
• Em dash clusters (max 1 per paragraph)
• "-ing" analyses: "highlighting the importance of..., ensuring that..."
• Inflated significance: "marking a pivotal moment in the evolution of..."

Step 3: Add soul

Step 4: Final check

Run the checklist below. If anything fails, fix and re-check.

TEMPLATES

Before/After

BAD (clean but soulless):
"Our cutting-edge platform leverages state-of-the-art AI to deliver
transformative solutions that empower businesses."

GOOD (has a pulse):
"We automate the boring stuff with AI so your team works on what
actually moves the needle. Set up in an hour, pays for itself in a week."

Product Description Structure

Line 1: What it does (plain language, no buzzwords)
Line 2: Who it's for
Line 3: Key differentiator (why this, not alternatives)
Line 4: Proof point (number, testimonial, or comparison)

Redline Template (for editing others' text)

[ORIGINAL]: "The innovative solution paradigm-shifts enterprise workflows"
[ISSUE]: Buzzword soup, no concrete meaning
[REWRITE]: "Cuts invoice processing from 3 days to 4 hours"
[WHY]: Specific result > vague claim

CHECKLIST

• [ ] No AI vocabulary (delve, crucial, tapestry, multifaceted...)
• [ ] No inflated significance (pivotal moment, indelible mark...)
• [ ] No "not just X; it's Y" constructions
• [ ] Em dash max 1 per paragraph
• [ ] Varied sentence lengths
• [ ] Author has opinion/position (not neutral report)
• [ ] Specific > general (numbers, names, examples)
• [ ] Final anti-AI pass completed

ANTI-PATTERNS

1. Over-humanizing technical docs -- documentation should be clear, not "soulful"
2. Replacing all structure with stream-of-consciousness -- structure is fine, sterile language is the problem
3. Adding fake personal anecdotes -- better to have no story than a fabricated one
4. Using the same humanization tricks every time -- "I keep thinking about..." gets stale too