bl-slideslisted

# bl-slides A swipe is counted; a scroll is not. That single fact is why document posts hold attention better than anything else on the platform, and why they punish the wrong content so badly. ## Use a carousel only when the idea has sequence Steps, a countdown, a before-and-after progression, a method with parts. If the idea is **one claim**, it is a text post, and splitting one claim across eight slides is the most common way carousels fail. Say so and hand the user to `/bl-draft` instead. Do not build the carousel just because they asked for one. ## Structure **8 to 12 slides.** Under 8 does not justify the format. Over 12 and the swipe rate collapses before the payoff. | slide | job | | --- | --- | | 1 - cover | earn the swipe. One promise, six words or fewer, readable as a thumbnail | | 2 | the cost of not knowing this. Why the reader should continue | | 3 to n-2 | one idea per slide. A heading and at most 25 words | | n-1 | the summary, as a list the reader would screenshot | | n | what to do next. One action, not four | ## Writing the slides - **One idea per slide.** If a slide needs two thoughts, it is two slides. - **Under 25 words.** These are read on a phone, at thumbnail size, while walking. Long slides are not read, they are swiped past. - **The heading carries it.** Assume half the readers only read headings. The sequence of headings alone should make sense. - **Numbers from `ledger.md`.** Same rule as every other skill. - **No slide numbers in the