r-bart Metadata
- inherits:
../writing-style/SKILL.md - applies to: X/Twitter, LinkedIn, Threads
Short-form voice adjustments
Voice resolution
The base voice still applies. Load it in this order:
scribetronic/style/writing-style.mdin the project root, if it exists — user's personalized override.- Bundled
writing-style/SKILL.mdtemplate otherwise.
This file lists the deltas — where short-form requires you to break or sharpen a long-form rule from whichever base loaded.
Why short-form is different
Three forces are stronger here than in long-form:
- The first 1-2 lines must earn the scroll-stop. No setup. The hook IS the first sentence.
- Density beats nuance. No room for the honest aside, the contrarian steelman, the worked example. Pick one move per piece.
- Closers are punches, not invitations. No "let me know in the comments" — it screams engagement-bait.
What's the same
- Voice, tone, anti-patterns from
writing-style/SKILL.mdall apply. - Numbers up front still wins.
- "Not just X, but Y" still banned.
- Coach-speak still banned.
- Em-dash > parens still preferred.
What changes
| Long-form rule | Short-form override |
|---|---|
| TL;DR up front | The hook IS the TL;DR. First line does both. |
| Sentence length variance (4-12-20-6) | Lean shorter. Most lines 3-12 words. One longer line for breathing. |
| Max 1 rhetorical question per piece | Same cap. But often the hook IS the question. |
| Paragraphs of 1-3 sentences | Single-line "paragraphs" are normal — visual rhythm via line breaks. |
| Cite tools/numbers/names | Even more critical. Specifics are 80% of why short-form posts work. |
| One staccato 2-3 word paragraph allowed ("That's it.", "Why?") | Still one cap. (Don't turn every line into a one-word jab.) |
Hook patterns that work
Use one of these openers, never neutral framing:
- The number reveal. "€0 in sales after 3 months. Here's why I'm not stopping."
- The contrarian assertion. "Choosing a niche is dead advice. Here's what to do instead."
- The unexpected admission. "I haven't shipped a single thing this week. Here's what I did instead."
- The list promise. "5 things I'd tell my 2024 self about launching solo. ↓"
- The specific scene. "3am, debugging a Stripe webhook that worked yesterday."
Closer patterns that work
Use one, never the soft exit:
- Repeat the thesis as a command. "Just ship."
- Specific next-action. "Try this for one week. Tell me if I'm wrong."
- One-liner reframe. "The conversation is the work."
- Sign-off with date/CTA. "Newsletter goes out Sunday. Link in bio."
Banned in short-form (in addition to base anti-patterns)
- "Hot take:" preface — show, don't label.
- "Hear me out…" — same.
- "Unpopular opinion…" — same. If it's actually unpopular, the post will prove it.
- Listing 5+ ideas that don't compose into one point. Pick one.
- Emoji bullet lists in LinkedIn (🔥 ✅ 🚀 X 5). Reads as 2018 spam.
- "What's your take? 👇" — engagement bait.
- "Save this for later 🔖" — engagement bait.
Platform-specific notes
X / Twitter
- Single posts: ~280 chars. Hook + payoff. No fluff.
- Threads: see
short-form-thread-from-longform/SKILL.md. - Line breaks every 1-2 sentences for scannability.
- 1300 char "see more" cutoff — first 3 lines must earn the click.
- Slightly more structure than X (2-4 short paragraphs OK).
- Still no emoji bullets.
- Carousels: see
short-form-carousel-li/SKILL.md.
Threads
- Closer to X in tone but tolerates slightly longer.
- Conversational > authoritative. Slightly more first-person, slightly less declarative-punch.
- Lower stakes — Threads is where you can be more playful with the rules.