Transform AI-generated text into authentic, voice-consistent content — not by faking humanity, but by applying real voice patterns from a specific person or brand.

• Rewrite AI drafts to match a specific person's voice
• Strip AI fingerprints from generated content before publishing
• Enforce voice consistency across AI-assisted content production
• Bridge the gap between AI efficiency and authentic brand expression
• Post-process any AI output (blog posts, emails, social, landing pages)

brand-voice-learner

• NN/g Voice and Tone research
• Brand voice analysis methodology (ClawFu

  brand-voice-learner

  )
• AI detection pattern research (GPTZero, Originality.ai signal analysis)
• WhatsApp IA NDD Camp community insights on AI content workflows

• Uniform sentence length (AI defaults to 15-20 words per sentence)
• Predictable paragraph structure (topic sentence → 3 supporting points → transition)
• Symmetrical lists (every bullet same length, same grammatical structure)
• Perfect parallelism in headers

• Corporate buzzwords nobody actually says: "delve," "landscape," "leverage," "robust," "streamline," "facilitate," "comprehensive"
• Filler openings: "In today's rapidly evolving...", "It's important to note that...", "In order to..."
• Over-hedging: "It's worth noting," "One might argue," "It could be said"
• Transition addiction: "Moreover," "Furthermore," "Additionally," "However" (every paragraph)

• No opinions (AI stays neutral by default)
• No contractions (AI under-uses them)
• Equal weight to everything (AI doesn't emphasize or deprioritize)
• Sanitized language (no edge, no personality, no risk)

AI FINGERPRINT SCAN:
□ Uniform sentence length? [yes/no]
□ Buzzword count: [N] instances
□ Transition density: [N] per paragraph
□ Contractions present? [yes/no]
□ Opinions/personality present? [yes/no]
□ Any sentence you'd never actually say? [list]

• Find the longest streak of same-length sentences. Break it.
• Add 2-3 short punches per section (under 8 words). "That's the point." "Not even close."
• Allow 1-2 longer flowing sentences if the voice uses them
• Fragments are OK if the voice uses fragments
• Dashes—for emphasis—if the voice does that
• Parentheticals (if the voice thinks while writing)

• Signature phrases or rhetorical moves
• Preferred sentence openers
• Opinion-stating patterns ("Ce n'est pas X. C'est Y." / "Here's the thing" / "Look,")
• Domain-specific vocabulary the voice always uses
• Structural habits (bullets vs. flowing prose, numbered lists vs. paragraphs)

• Apply contraction level matching the voice (some voices never contract, some always do)
• Check register: is the formality level consistent with the voice?
• Verify pronoun usage matches (some voices are "nous," some are "je," some are "on")

• Would [person] actually say this?
• Does it flow at their pace?
• Is there any word they'd never use?

[The input text]

• Vocabulary: [3-5 key word swaps]
• Rhythm: [What changed structurally]
• Voice markers: [What was injected from the voice profile]
• Removed: [What AI signals were stripped]

"In today's rapidly evolving digital landscape, leveraging AI-powered tools has become essential for businesses seeking to maintain their competitive edge. Moreover, organizations that fail to adopt these comprehensive solutions risk falling behind in an increasingly automated marketplace."

Tout le monde dit qu'il faut "adopter l'IA" pour rester compétitif. Ce n'est pas un problème d'adoption. C'est un problème de savoir quoi en faire.

La plupart des boîtes installent des outils IA comme on installe un ERP — par obligation, sans stratégie. Résultat : elles automatisent leurs erreurs plus vite.

• Vocabulary: "landscape" → cut, "leveraging" → cut, "comprehensive solutions" → cut, "competitive edge" → reframed as the actual problem
• Rhythm: Broke uniform long sentences into short punch + development
• Voice markers: "Ce n'est pas X. C'est Y." recadrage, opinion ("par obligation, sans stratégie"), concrete metaphor (ERP)
• Removed: "In today's...", "Moreover", hedging, the entire premise (flipped it)

"We are pleased to announce that our platform now offers a comprehensive suite of analytics tools designed to empower teams to make data-driven decisions. These robust features include real-time dashboards, automated reporting, and customizable metrics tracking."

Here's the thing — we just shipped analytics. Real dashboards, automated reports, and metrics you actually set up yourself.

No more exporting CSVs at 11pm to make a chart for Monday's meeting. Your data's right there. Live.

• Vocabulary: "pleased to announce" → "just shipped," "comprehensive suite" → cut, "empower" → cut, "robust" → cut, "customizable" → "you actually set up yourself"
• Rhythm: Long formal sentences → short punchy + one fragment ("Live.")
• Voice markers: "Here's the thing" opener, contractions (we're, that's, your data's), relatable scenario (CSVs at 11pm)
• Removed: All corporate filler, passive construction, feature-first framing (replaced with problem-first)

"Implementing a microservices architecture requires careful consideration of service boundaries, inter-service communication protocols, and data consistency patterns. Organizations should ensure that their teams possess the requisite expertise to manage the increased operational complexity inherent in distributed systems."

Microservices sound great in conference talks. In practice, they mean your team now manages 40 tiny services instead of one big app — and every service needs to talk to every other service without losing data along the way.

The question isn't whether microservices are better. It's whether your team can handle the operational overhead. If you're struggling with one monolith, splitting it into 40 pieces doesn't fix the problem. It multiplies it.

• Vocabulary: "requisite expertise" → "whether your team can handle," "inherent in" → cut, "ensure" → cut
• Rhythm: Dense abstract sentences → analogy + rhetorical question + concrete scenario
• Voice markers: "In practice" pivot, rhetorical question, analogy (40 tiny services), opinion in closing line
• Removed: Passive voice, abstract recommendations, jargon without explanation

• Rewriting AI text to match a specific documented voice
• Stripping AI detection signals systematically
• Enforcing voice consistency across content types
• Bridging AI efficiency with authentic voice expression

• Create a voice from nothing (you need samples or a profile)
• Guarantee undetectable output (detectors evolve, and the goal isn't deception anyway)
• Replace genuine expertise (voice-matched text that's factually wrong is still wrong)
• Work well with minimal voice input (garbage in → generic out)

1. An arms race with detectors you'll lose
2. Not what good writing looks like
3. Unnecessary if you have a real voice to inject

• "Tighten the voice — it's still too formal for [name]"
• "Rewrite just paragraph 3, the rest is good"
• "Switch to [channel] register (social instead of blog)"
• "The opinion isn't strong enough — [name] would take a harder stance here"
• "Run the AI fingerprint scan on this new draft"

• NN/g Voice and Tone Guidelines
• ClawFu

  brand-voice-learner

  skill (voice analysis methodology)
• AI detection research: GPTZero, Originality.ai signal patterns

• WhatsApp IA NDD Camp — Cyril Frémont's "mega prompt" for AI text humanization (inspiration for the kill list, reframed from deception to authenticity)

• brand-voice-learner — Extract voice patterns from existing content (prerequisite)
• copywriting-ogilvy — Writing craft foundations
• seo-content-writer — SEO content that needs voice enforcement post-generation
• llm-optimized-content — GEO content that needs voice injection for E-E-A-T
• storytelling-storybrand — Narrative voice framework