Write long-form content that sounds like a real person or brand, rather than generic AI-generated content.
When to Activate
- Draft blog posts, essays, release notes, guides, tutorials, or newsletters
- Turn notes, interview transcripts, or research materials into polished articles
- Mimic the voice of an existing founder, operator, or brand based on examples
- Optimize the structure, pacing, and supporting evidence of already-written long-form copy
Core Rules
- Start with something concrete: an example, output, anecdote, number, screenshot description, or code block.
- Explain after the example, not before.
- Prefer short, direct sentences and avoid lengthy padding.
- Use verifiable specific numbers.
- Strictly prohibit fabricating personal biographies, company metrics, or customer testimonials.
Voice Capture Workflow
If the user needs a specific voice, collect one or more of the following materials:
- Published articles
- Newsletters
- X / LinkedIn posts
- Documents or memos
- A brief style guide
Then extract:
- Sentence length and rhythm
- Whether the tone is formal, conversational, or sharp
- Preferred rhetorical devices, such as parentheses, lists, fragments, or questions
- Acceptance of humor, opinions, and contrarian framing
- Formatting habits, such as headings, bullet points, code blocks, and pull quotes
If no voice reference is provided, default to a direct operator-style: specific, practical, and without exaggeration.
Banned Patterns
Delete and rewrite the following:
- Generic openings, such as "In today's rapidly evolving landscape"
- Filler transitions, such as "Moreover" and "Furthermore"
- Exaggerated words, such as "game-changer", "cutting-edge", or "revolutionary"
- Vague claims lacking evidence
- Biographical or credibility claims not substantiated by the provided context
Writing Process
- Clarify the audience and purpose.
- Build a skeleton outline, with one clear purpose per section.
- Start each section with evidence, an example, or a scenario.
- Expand only when the next sentence truly has value.
- Remove anything that sounds like a template or self-promotion.
Structure Guidance
Technical Guides
- Start with what the reader will gain
- Use code or terminal examples in each major section
- End with concrete takeaways, not a soft summary
Essays / Opinion Pieces
- Open with a conflict, contradiction, or sharp observation
- Keep a single argument thread per section
- Use examples that support the point
Newsletters
- Keep the above-the-fold content engaging
- Combine insights with updates rather than filling with daily trivia
- Use clear section labels and an easy-to-scan structure
Quality Gate
Before delivery:
- Verify factual statements against the provided sources
- Remove filler words and corporate tone
- Confirm the tone matches the provided examples
- Ensure each section adds new information
- Check the formatting for the target platform