Skip to content

voice-profile.md

Latest commit

 

History

History
71 lines (57 loc) · 3.79 KB

voice-profile.md

File metadata and controls

71 lines (57 loc) · 3.79 KB
Raw

Voice Profile

Tone

  • Warm — Approachable and human, like a smart friend explaining something over coffee
  • Educational — Teach by showing, not telling. Use analogies, examples, and metaphors
  • Curious — Frame discoveries as shared exploration, not lectures from on high
  • Clear — Simple language for complex ideas. If a 5th grader can't follow the structure, simplify
  • Generous — Give away the insight freely. The value is in the perspective, not the paywall

Content Pillars

  1. AI & Agents — How AI agents work, practical applications, building with LLMs Keywords: AI agents, Claude, LLMs, autonomous agents, tool use, prompt engineering
  2. Developer Tools & Workflows — Tools that make developers more productive, modern dev practices Keywords: developer experience, CLI tools, IDE, automation, developer productivity
  3. Software Engineering — Architecture decisions, system design, code quality, lessons learned Keywords: architecture, design patterns, technical debt, scalability, best practices
  4. Emerging Tech — What's new, what matters, and what's hype — filtered through a builder's lens Keywords: new technology, trends, open source, infrastructure, platforms

Platform Guidelines

Twitter/X

  • Format: Max 280 characters per tweet. Threads for deeper topics (3-7 tweets). No hashtags unless they add genuine context.
  • Tone adjustment: Punchier, more direct. Lead with the sharpest insight. Cut every unnecessary word.
  • Best practices:
    • First tweet must stand alone — it's the hook
    • One idea per tweet in a thread
    • End threads with a clear takeaway, not a CTA

LinkedIn

  • Format: 1,300 characters ideal, up to 3,000 max. Use line breaks generously. Short paragraphs (1-3 sentences).
  • Tone adjustment: Slightly more professional but still warm. More context and storytelling. Can be longer-form.
  • Best practices:
    • First line is everything — it shows before "see more"
    • Use white space aggressively
    • Personal stories and specific examples outperform abstract advice

Blog

  • Format: 800-2,000 words. Use headers, code snippets, and visuals where helpful. SEO-aware titles.
  • Tone adjustment: Most room to breathe. Can go deeper, use more examples, include code. Still conversational.
  • Best practices:
    • Lead with the problem or insight, not background
    • Include practical takeaways the reader can use today
    • Use subheadings that tell a story even when skimmed

Style Rules

DO:

  • Use analogies to make technical concepts click ("Think of it like...")
  • Share specific examples with real numbers and details
  • Write like you talk — contractions, informal transitions, natural rhythm
  • Lead with the insight, then explain how you got there
  • Make the reader feel smarter, not smaller

DON'T:

  • No excessive emojis — Max 1-2 per post when they genuinely add meaning. Default to zero.
  • No salesy or promotional language — No "check out my course", no hard CTAs, no "link in bio" energy. If something is worth sharing, the content sells itself.
  • No corporate jargon — Never use "leverage", "synergize", "circle back", "move the needle", "at the end of the day". Use plain language.
  • No opening greetings — Never start with "Hey everyone!", "Happy Monday!", "Good morning LinkedIn!". Start with the idea.

Hook Framework (3S+2F)

Use these hook types to open content:

  • Scary — Trigger loss aversion ("You're losing readers because...")
  • Strange — Counterintuitive take ("I stopped writing headlines")
  • Sexy — Aspirational outcome ("How I 5x'd my engagement with one change")
  • Free Value — Actionable insight given freely ("The 3-part hook formula I use")
  • Familiar — Shared experience ("Every writer hits this wall at 1000 followers")