What problem does it solve? Deciding how each slide page should look—chart, bullets, diagram, image, or comparison—is a slow, inconsistent judgment call, and hand-written visual specs often cannot be rendered directly by downstream tooling. This Skill converts an already-paginated slide plan into a render-ready per-page visual spec. ## Core Features & Use Cases - Content-to-layout decision rules: Maps each page's type, content points, and information density to one of nine layout archetypes (title, big-statement, bulleted-list, two-column-compare, data-chart, process-diagram, image-led, quote, closing-CTA) using a decision framework based on Zelazny and Minto. - pptxgenjs primitive mapping: Translates titles and content points into visual elements that map 1:1 to pptxgenjs primitives (addText, addTable, addChart, addShape, addImage), so the downstream slide-pptx skill can render them directly. - Brand-aware design notes: Loads brand colors, type scale, and image rules from a configurable brand source, with neutral fallbacks, and enforces restraint rules like one decision color per page. - Use Case: After slide-page-splitter produces a SLIDE_PACKET ▸ Pages packet for a sales deck, run this Skill to decide that the revenue page becomes a sorted bar chart, the options page becomes a two-column comparison, and the closing page becomes a CTA, then hand the spec to slide-pptx for rendering. ## Quick Start Take this SLIDE_PACKET ▸ Pages handoff and decide the visual treatment for each page, producing a render-ready SLIDE_PACKET ▸ Visuals spec for slide-pptx.
