✍️ For creatorsFrameworks from public writing skills: tweet-writer (hook formulas / PAS), Hormozi's four parts, Dan Koe's rhythm
Short-post outline
Three hook options (the hook decides 80–90% — write it first)
- Specific result:“FFmpeg-GUI-Editor-Windows breaks out on GitHub” — wave height 63, 1 sources reporting at once.
- Curiosity gap:New breakout on GitHub: 2,339 stars in 3 days, about 780 a day; a graphical interface edit But the thing worth watching is not the event itself.
- Signal:The signal is not where the noise is: “FFmpeg-GUI-Editor-Windows breaks out on GitHub” is already at #40 and still developing.
Body skeleton · PAS (Problem → Agitate → Facts)
- Problem:New breakout on GitHub: 2,339 stars in 3 days, about 780 a day; a graphical interface edit
- Agitate:Record only.
- Facts:New breakout on GitHub: 2,339 stars in 3 days, about 780 a day; a graphical interface editor for FFmpeg (Windows).
Wave 63 · rank #40 · 1 sources in resonance · Sources:github.com
Short-post tips
- Shorter wins: one breath per post; under ~110 characters performs best for single posts (tweet-writer).
- The first hour is critical: post when your audience is active; put links at the end or in a reply, not up front.
- Specific numbers beat adjectives: 'wave 209, 5 sources at once' over 'it's huge'.
- Rotate hook formulas: specific result / curiosity gap / contrarian / question / story.
- In a thread, every post must stand alone; the first one must work as a standalone hook.
Long-form outline
Skeleton · Hormozi's four parts (Idea → Story → Reasons → Soft CTA)
- One idea:State your claim in one sentence — distill it from the suggested action; if you can't, the angle isn't clear yet
- Story & evidence:FFmpeg-GUI-Editor-Windows breaks out on GitHub → FFmpeg-GUI-Editor-Windows breaks out on GitHub(Wave trail:63)
- Reasons, not steps:One reason each from the tech, business and user angles — argue why it is true, not how to do it
- Soft CTA:End lightly: I will keep tracking its wave height — bookmark this page to follow along
Long-form tips
- One piece, one idea: if the claim does not fit in one sentence, do not start writing (Hormozi).
- Reasons, not steps: argue the idea from psychological, economic, behavioral and competitive angles — aim for 4–6.
- Rhythm after Dan Koe: ~40% ultra-short paragraphs, ~40% conversational medium, ~20% longer expansive passages.
- Pick the angle before drafting: list several angles for the same topic, take the one with the most new information (Substack workflow).
- Persuasion is concrete: real numbers, real cases, a timeline — adjectives are the cheapest currency.