Linkedin Post

LinkedIn Post Creator

Create engaging LinkedIn posts in your authentic brand voice.

Before Writing

1. Run the rhetoric selector to get your rhetorical devices:

   python shared/rhetoric_selector.py --type linkedin_technical
   # or --type linkedin_provocative
   # or --type linkedin_personal

2. Review the voice guide: See VOICE_GUIDE.md

3. Check content pillars: See CONTENT_PILLARS.md

Post Structure

The Hook (First 2-3 lines)

• This is what shows before "...see more"
• Must stop the scroll
• Use a provocative statement, surprising fact, or bold claim
• Rhetorical devices work brilliantly here (antithesis, hyperbaton)

The Body

• Short paragraphs (1-3 sentences each)
• Use line breaks liberally - walls of text don't work
• Include specifics: numbers, real examples, code snippets if relevant
• Build your argument or tell your story
• This is where anaphora, tricolon, and anadiplosis shine

The Closing

• End with a question, takeaway, or soft CTA
• Questions drive comments
• Epistrophe and chiasmus work well for memorable endings
• ONE CTA maximum (if any)

Formatting Rules

• Optimal length: 1,000-1,300 characters
• Maximum: 3,000 characters (but shorter is usually better)
• Line breaks: After every 1-2 sentences
• Emojis: Use sparingly if at all (max 1-2, and only if natural)
• Hashtags: 3-5 at the end, relevant to topic

Templates by Content Type

See templates folder:

• Technical Tip
• Industry Take
• Personal Story

Voice Reminders

From your VOICE_GUIDE.md:

• Write in your authentic voice as defined in the guide
• Use the phrases and patterns you've identified
• Avoid the words and phrases on your "avoid" list
• Maintain the spelling conventions you've chosen

Phrases that often work well

• "Here's the thing..."
• "Look," (to start a provocative point)
• "The uncomfortable truth is..."
• "Nobody talks about this, but..."
• "I was wrong about..."

Generally avoid

• "Excited to announce..."
• "Game-changer" / "Revolutionary"
• "Thought leader"
• Corporate jargon

Example Post Structures

Technical (with tricolon and litotes)

[HOOK: What nobody tells you about X]

[Brief context - why this matters]

[The insight - short, punchy sentences]

[Example - real numbers, real code if relevant]

[Takeaway - what to do with this]

[Closing question to drive comments]

#YourHashtags #Here

Provocative (with antithesis and anaphora)

[HOOK: Bold claim or contrarian statement]

[Context that sets up the contrast]

[Build your argument using repetition]
You don't need X. You don't need Y. You don't need Z.

[The uncomfortable truth]

[Your stance - what you believe]

[Invitation for discussion]

#YourHashtags #Here

Quality Checklist

Before posting, verify:

• [ ] Hook stops the scroll (would YOU click "see more"?)
• [ ] Voice is authentically yours (check against your guide)
• [ ] At least one rhetorical device used naturally
• [ ] Specific examples or numbers included
• [ ] No corporate jargon
• [ ] Under 1,500 characters (ideally)
• [ ] CTA is soft and earned (if present)
• [ ] 3-5 relevant hashtags

Template: Industry Take / Hot Take Post

Best rhetoric devices

• Antithesis for contrasting positions
• Anaphora for building your argument
• Hyperbaton for attention-grabbing openings

Structure

[HOOK: Bold claim or controversial statement]

[THE SETUP: Why this matters / context]

[THE ARGUMENT: Your position with evidence]
- Use anaphora here if building momentum
- Or antithesis if contrasting two approaches

[THE UNCOMFORTABLE TRUTH: What nobody wants to admit]

[THE CALL: What should change / what you believe]

[OPTIONAL: Question to spark debate]

#YourIndustry #YourNiche [+ relevant tags]

Example Structure

The [industry] has a dirty secret.

They don't want you to [know/learn/do something].

Every [person] who discovers [alternative] is a customer they lose.
Every [team/company] that [makes the switch] is [revenue] they can't collect.
Every success story with [your approach] is a threat to their model.

So they make it complicated.

They [obstacle 1].
They [obstacle 2].
They [obstacle 3].

I'm not saying they're evil. I'm saying their incentives
and your interests are not aligned.

The uncomfortable truth: the best [solution] for your [problem]
might be the one that [unexpected characteristic].

Worth considering before [relevant decision point].

#YourIndustry #YourNiche #RelevantTopic

Variations

"Myth busting" angle

[THE MYTH everyone believes]
[WHY it's wrong]
[THE REALITY]
[WHAT THIS MEANS for you]

"Prediction" angle

[WHAT'S CHANGING in the industry]
[WHY it's happening now]
[WHAT THIS MEANS]
[HOW TO PREPARE]

"Contrarian" angle

[POPULAR OPINION]
"Actually..." [Your counter-take]
[YOUR EVIDENCE]
[THE NUANCE most people miss]

Voice notes for hot takes

• Take a clear stance - fence-sitting is boring
• Back opinions with experience, not just opinion
• "I could be wrong, but..." is okay occasionally
• Invite disagreement - engagement is the goal
• Don't punch down - criticise systems, not people
• Be provocative, not offensive
• Have evidence or experience to back your claims

Template: Personal Story Post

Best rhetoric devices

• Anadiplosis for narrative flow
• Litotes for humble understatement
• Hyperbaton for reflective moments

Structure

[HOOK: Time marker + surprising outcome or lesson]

[THE SETUP: What I thought / what I was doing]

[THE TURNING POINT: What happened / what changed]

[THE LESSON: What I learned from this]

[THE APPLICATION: How this applies to you / the reader]

[CLOSING: Reflection or question]

#CareerLessons #YourIndustry [+ relevant tags]

Example Structure

Three years ago, I nearly gave up on [your field].

I'd spent [time period] [doing something]. [Describe it].
[More detail about the effort].

[The person/situation] hated it.

Not because it was wrong. Because it was right. It showed
them [uncomfortable truth]. I'd [delivered/built/created] exactly
what they asked for.

But not what they needed.

That project taught me something I wish I'd learned earlier:
[the lesson in one clear sentence].

[Expand on the lesson - what it means in practice]

Now I start every [project/engagement] with one question:

"[The question that captures your lesson]"

If they can't answer, we're not ready to [start/proceed] yet.

What [type of experience] taught you the most?

#LessonsLearned #YourIndustry #CareerGrowth

Variations

"Failure" angle

[THE FAILURE: What went wrong]
[THE CONTEXT: Why I thought it would work]
[THE REALISATION: When I understood]
[THE LESSON: What I do differently now]

"Journey" angle

[WHERE I WAS: Starting point]
[THE CHALLENGE: What I faced]
[THE CHANGE: What shifted]
[WHERE I AM NOW: Current state]
[THE TAKEAWAY: What this taught me]

"Realisation" angle

[THE ASSUMPTION: What I used to believe]
[THE MOMENT: When it clicked otherwise]
[THE NEW UNDERSTANDING]
[WHY THIS MATTERS]

Voice notes for personal stories

• Be genuinely vulnerable - not performatively
• Stories where you're NOT the hero often work best
• Specific details make it real (exact amounts, time periods, page numbers)
• Always end with something useful for the reader
• "I was wrong" is more powerful than "I was right"
• Litotes works brilliantly here - understate your successes
• Let the story speak - don't over-explain the lesson

Template: Technical Tip Post

Best rhetoric devices

• Tricolon for listing steps or features
• Asyndeton for punchy instruction sequences
• Litotes for understated observations

Structure

[HOOK: Surprising insight or "here's what nobody tells you"]

[CONTEXT: Brief setup - why this matters]

[THE TIP: The actual technical insight]
- Bullet points work well for technical concepts
- Or short numbered steps
- Keep each point scannable

[EXAMPLE: Real code, real numbers, real results]

[TAKEAWAY: What to do with this knowledge]

[OPTIONAL CTA: Question or soft call to action]

#YourRelevant #Hashtags #Here

Example Structure

Here's a [topic] trick that took me years to discover.

You can [surprising capability or shortcut].

I was [the hard way you used to do it]. [Describe the
struggle briefly].

Then I found [the better approach].

[Show the solution - code, steps, or process]

[Brief explanation of why it works]

The documentation mentions it. Briefly. On page 47.

Sometimes the best features are the ones nobody talks about.

What's your favourite hidden [topic] feature?

#YourIndustry #YourTool #YourNiche

Variations

"Common mistake" angle

[HOOK: The mistake you see everywhere]
[WHY it happens]
[THE FIX: What to do instead]
[PROOF: Show the difference]

"Before/after" angle

[HOOK: The old way sucked]
[BEFORE: What you used to do]
[AFTER: The better approach]
[RESULT: The improvement]

"Quick tip" angle (shorter format)

[TIP in one sentence]

[Why it works - 2-3 sentences]

[Example if needed]

That's it. Simple but effective.

Voice notes for technical posts

• Teaching tone, but still opinionated
• Show real code, real numbers
• "Here's what actually works..."
• Share shortcuts you've learned
• Be specific - vague tips don't help anyone