li-post

1# li-post
2 
3Turns one raw idea into a LinkedIn post that sounds like the person who
4posted it.
5 
6## Before you write
7 
81. Read `~/.claude/linkedin/voice.md` if it exists. That file is the user's
9   voice profile: how they talk, what they never say, who they are talking to.
10   If it does not exist, ask for **three of their own past posts**, infer the
11   voice from those, and write the file. Do not skip this and do not invent a
12   voice. A post in the wrong voice is worse than no post.
132. Read `hooks.json` in this folder. All 21 formulas, with templates, filled
14   examples, what each is for, and how each one usually gets ruined.
153. If the idea is thin - "post about AI" - do not pad it. Ask one batched
16   question: what happened, to whom, and what did it cost or return. A post
17   needs one specific true thing. Get it before writing.
18 
19## The shape
20 
21LinkedIn rewards dwell time, saves and comments, in that order. So:
22 
23```
24Line 1     the hook. Alone. It has to survive truncation at ~140 chars mobile.
25Line 2     the payoff of line 1, not setup for line 3.
26Body       short paragraphs, 1-3 lines each, blank line between every one.
27           No wall. The white space is the format.
28The turn   one line that reframes what came before.
29Close      one specific question, or one instruction. Never both.
30```
31 
32Length: 900-1,300 characters is the working range for a text post. Under 400
33reads as a thought, not a post. Over 2,000 needs to earn every line, and the
34…