What problem does it solve? Turning a presentation storyline into actual slides requires deciding how many pages each narrative beat becomes, what each page says, and how much information fits per page. Doing this ad hoc produces overcrowded slides, vague titles, and decks that lose the narrative thread. ## Core Features & Use Cases - Beat-to-page expansion: Applies three paging principles (one point per page, titles that carry their own conclusion, narrative-rhythm skeleton pages) to decide how many pages each storyline beat splits into. - Per-page content allocation: Assigns each page a page type from a fixed enum (title / section / content / data / quote / closing), 3-5 content bullets capped at two hierarchy levels, and an information density tag (低 / 中 / 高). - Human review and relay handoff: Lists the full page list for numbered keep/delete/merge/split review, then outputs a SLIDE_PACKET ▸ Pages handoff packet for the next leg, slide-visual-selector. - Use Case: You receive a SLIDE_PACKET ▸ Storyline from slide-storyline-designer for a 12-page pitch deck. This Skill expands each beat into pages, writes conclusion-first titles, tags density, confirms the list with you, and hands off a render-ready page skeleton. ## Quick Start Paste the SLIDE_PACKET ▸ Storyline handoff packet and ask the assistant to split it into a page-by-page slide list with titles, bullets, and information density.
